As a packager new to Fedora's system, and perhaps because I failed to read the output in my terminal, I failed to immediately grok that a 'cvs up' was required after cvs-import.sh but before 'make build' The wording around issuing that command leads one (or at least me) to believe that it is automagically handled by cvs-import.sh, and only necessary if you manually moved files into each branch. Thoughts? --ke4qqq 13:28, 19 January 2009 (UTC)
In my attempt to be a first time packager, it turned out that you need to do two packages - or review another package - to be sponsored. I didn't budget the time for the 2nd package/review, so had to bow out for a while. Just a heads up for any other busy person wanting to contribute just a few packages. Sdgathman 02:08, 3 May 2010 (UTC)
Finally (if you haven't set up an other editor) vi will open up to let you edit the CVS changelog. For the changelog, use the same format as the end of the .spec file
Really?! This can't be right. --Spike 18:54, 12 July 2010 (UTC)
"click on 'request new package' and fill in the desired information" leaves something to be desired. Should you select only master and the next release for collections or can the new package be added to the current release? What do the fields "Monitor this package and report new versions" and "Koschei integration" do? --Dulsi (talk) 03:47, 27 August 2016 (UTC)
It's now possible to push changes to forks in src.fedoraproject.org, see here: Infrastructure/HTTPS-commits --Ykorman (talk) 18:46, 27 June 2020 (UTC)