2:22 p.m.
I've been doing development on a Fedora 12 system and have a spec file, our original
source code from our external git repository, and patches to be applied by the spec file
for the Fedora build.
How do I actually get source code into Fedora N (N=12) to be built and available in a
repository?
I've tried find documentation, but I guess I'm not putting in the right keywords.
4 p.m.
On Thu, Mar 11, 2010 at 03:22:16PM -0500, Scott Salley wrote:
I've been doing development on a Fedora 12 system and have a
spec
file, our original source code from our external git repository, and
patches to be applied by the spec file for the Fedora build.
How do I actually get source code into Fedora N (N=12) to be built
and available in a repository?
I've tried find documentation, but I guess I'm not putting in the
right keywords.
OK, so it sounds like you've been following the packaging guidelines,
right?
https://fedoraproject.org/wiki/Packaging:Guidelines
The page I think you are looking for is here, which has steps for
becoming a package maintainer:
http://fedoraproject.org/wiki/Join_the_package_collection_maintainers
One thing that you might want to pluck out of the steps and do it
earlier is getting yourself setup to use Koji, where you can do
scratch builds before your package is finished review.
http://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Ins...
Let us know how it works out,
- Karsten
--
name: Karsten 'quaid' Wade, Sr. Community Gardener
team: Red Hat Community Architecture
uri: http://TheOpenSourceWay.org/wiki
gpg: AD0E0C41
11:33 a.m.
Thank you for your help. I've uploaded my package for review and now I'm waiting
for comments/sponsorship/blessings.
How long does the review process generally take? Is there anything I can do to help it
along (aside from responding to review criticism)?
-----Original Message-----
From: isv-sig-bounces(a)lists.fedoraproject.org [mailto:isv-sig-
bounces(a)lists.fedoraproject.org] On Behalf Of Karsten Wade
Sent: Thursday, March 11, 2010 2:01 PM
To: isv-sig(a)lists.fedoraproject.org
Subject: Re: Hosting and building questions.
On Thu, Mar 11, 2010 at 03:22:16PM -0500, Scott Salley wrote:
> I've been doing development on a Fedora 12 system and have a spec
> file, our original source code from our external git repository, and
> patches to be applied by the spec file for the Fedora build.
>
> How do I actually get source code into Fedora N (N=12) to be built
> and available in a repository?
>
> I've tried find documentation, but I guess I'm not putting in the
> right keywords.
OK, so it sounds like you've been following the packaging guidelines,
right?
https://fedoraproject.org/wiki/Packaging:Guidelines
The page I think you are looking for is here, which has steps for
becoming a package maintainer:
http://fedoraproject.org/wiki/Join_the_package_collection_maintainers
One thing that you might want to pluck out of the steps and do it
earlier is getting yourself setup to use Koji, where you can do
scratch builds before your package is finished review.
http://fedoraproject.org/wiki/Join_the_package_collection_maintainers#I
nstall_the_Client_Tools_.28Koji.29
Let us know how it works out,
- Karsten
--
name: Karsten 'quaid' Wade, Sr. Community Gardener
team: Red Hat Community Architecture
uri: http://TheOpenSourceWay.org/wiki
gpg: AD0E0C41
3:13 a.m.
Scott Salley wrote:
Asking for help is never frowned upon! ;-)
You've done that already, I know, but hear me out.
There's lots of review requests pending, and fewer people working on getting
those reviews done. They're not handled in order of submission, but are
subject to a little bit of community self-regulation if you will, in that
whomever is interested may sink his teeth into reviewing the package.
The more noise you give it (the more you communicate about it), the better the
chances are you find that person who's interested in either the package or in
helping you out. Regrettably, not many of those people are on this list -I
think.
devel(a)lists.fedoraproject.org though is a huge list with a lot of traffic full
of people willing to do *something*.
Another means may be a blog post or two or three on how your progressing with
your package and becoming a packager, especially if those blog posts end up on
our planet[1].
Mind that a URL to the review request you submitted might help as well ;-)
Hope this helps!
-- Jeroen
[1] http://planet.fedoraproject.org
Thank you for your help. I've uploaded my package for review and
now I'm
waiting for comments/sponsorship/blessings.
How long does the review process generally take? Is there anything I can do
to
help it along (aside from responding to review criticism)?
8:20 p.m.
On Fri, Apr 09, 2010 at 10:13:52AM +0200, Jeroen van Meeuwen wrote:
The more noise you give it (the more you communicate about it), the better the
chances are you find that person who's interested in either the package or in
helping you out. Regrettably, not many of those people are on this list -I
think.
All great points, yep. Might be worth mentioning this SIG is a
gateway to Fedora contributing for ISVs. :) There is a bit of
noisiness required[1] to activate the human filter properly. For
example, repeating messages a few times in separate posts, showing
updates in each post, gives the best chance for being noticed by the
broadest audience. Multiply that by media (devel@, Fedora Planet,
etc.)
- Karsten
[1]
https://www.theopensourceway.org/wiki/How_to_loosely_organize_a_community....
--
name: Karsten 'quaid' Wade, Sr. Community Gardener
team: Red Hat Community Architecture
uri: http://TheOpenSourceWay.org/wiki
gpg: AD0E0C41
12:52 p.m.
On Fri, Apr 09, 2010 at 10:13:52AM +0200, Jeroen van Meeuwen wrote:
Scott Salley wrote:
> Thank you for your help. I've uploaded my package for review and now I'm
waiting for comments/sponsorship/blessings.
>
> How long does the review process generally take? Is there anything I can do
to help it along (aside from responding to review criticism)?
>
Asking for help is never frowned upon! ;-)
You've done that already, I know, but hear me out.
There's lots of review requests pending, and fewer people working on getting
those reviews done. They're not handled in order of submission, but are
subject to a little bit of community self-regulation if you will, in that
whomever is interested may sink his teeth into reviewing the package.
The more noise you give it (the more you communicate about it), the better the
chances are you find that person who's interested in either the package or in
helping you out. Regrettably, not many of those people are on this list -I
think.
devel(a)lists.fedoraproject.org though is a huge list with a lot of traffic full
of people willing to do *something*.
Another means may be a blog post or two or three on how your progressing with
your package and becoming a packager, especially if those blog posts end up on
our planet[1].
Mind that a URL to the review request you submitted might help as well ;-)
Hope this helps!
Also, it's important to remember that *packagers* get sponsored, as
opposed to packages. Many sponsors will want to see evidence that the
packager is going to "do their part" for the rest of the community and
do one or more package reviews themselves. Since the guidelines are
all written on the wiki, it's possible for a new packager to compare
any package in the queue against the guidelines and do a review. That
package, in turn, isn't being sponsored -- its packager is.
By doing this we can better scale the efforts of our packaging
community -- people are trusted to maintain packages because they've
shown they are willing to help the rest of the community perform this
process, which can take a bit of time.
When you submit a package for review, you can also point to the
reviews you've done which will also help get sponsorship faster.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
Where open source multiplies: http://opensource.com
5135
days inactive
5170
days old
isv-sig@lists.fedoraproject.org
5 comments
4 participants
participants (4)
-
Jeroen van Meeuwen -
Karsten Wade -
Paul W. Frields -
Scott Salley