-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Till Maas wrote: > On Sunday 02 September 2007 16:40:42 Mike McGrath wrote: > >> I'm literally asking people for help. I'm saying we don't have enough >> man power to make the tools work the way you want to. And you're saying >> you "dislike it"? How do you think the we feel about it? > >> Keep in mind that very few people with the @redhat.com address actually >> get paid full time to work on Fedora. Many of them do it just like you >> do in their spare time. >> >> Please help! I'm on my knees begging anyone with python experience. >> Help us volunteers help us! You're our only hope! > > What can one really do? I submitted a patch[1] for a big annoyance in Koji: > build logs are not easily accessible. The patch is now 3 months old and got > applied recently to the internal repository but it is still not in the > deployed Koji. This is very depressing, especially because I needed access to > build logs a dozend times since then. This not only affects koji, but also > bodhi where I provided several simple patches that are still not available in > the deployed version. Same for Makefile.common, where there was only little > Feedback. Also the documentation in and about koji and bodhi is not very > good, which makes providing patches even harder. > > So it seems the only way to really change something here is to get commit > access to the projects and access to the deployment servers, but this is imho > a pretty high barrier. > Depends on what you want to do and what projects you want to work on. For people who want to code on the packagedb, I've been setting up test instances on publictest1.f.r.c and giving the contributor access to a branch. When they have something that works, I can easily check both their changes at a code level by diffing the branch and at the "view what their changes do" level via the test instance. It's then easy to merge their changes or give feedback about what I'd like to see developed more. This is how both the new packagedb template (thanks to ricky) and user pages (thanks to nigelj) were developed. There's other things that could be done by people who don't want to code. For instance, I could use someone to help out with releases. This could be as simple as me deciding when a release needs to be made and the other person creating an rpm to distribute to the app servers. Or if the person has more time, they could have a stable branch and they could pull changes from the development branch(es) of features that they think are stable enough. I don't know if the koji hackers (mbonnet is my main point of contact) or bodhi hacker (lmacken) have thought about ways that they could divide up the many tasks that they have to do to go from identifying problems (tickets really help here) to implementing solutions (designing and coding) to getting a new version out with the fix in place (updating a stable branch, making a release, getting the release into infrastructure) but if you ask I'll bet they could identify some areas that they need help with. - -Toshio -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFG2wRxX6yAic2E7kgRAoA/AJ0duQ8KuTx5eHYvJgYcHLj/fjI4UwCgjne6 I+FuNpCaq9jYKncOYVW97p8= =StPJ -----END PGP SIGNATURE----- -- Fedora-maintainers mailing list Fedora-maintainers@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers -- Fedora-maintainers-readonly mailing list Fedora-maintainers-readonly@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly
