From 59b94496588c4a33c17684fe874f8ea1f15cea06 Mon Sep 17 00:00:00 2001 From: Chris Frey Date: Mon, 12 Mar 2012 20:40:49 -0400 Subject: [PATCH] Removed Debian maintainer from AUTHORS, and merged deputy docs into TODO list --- AUTHORS | 26 ------------ DEPUTY | 147 ---------------------------------------------------------------- TODO | 75 +++++++++++++++++++++++++++++++++ 3 files changed, 75 insertions(+), 173 deletions(-) delete mode 100644 DEPUTY diff --git a/AUTHORS b/AUTHORS index 9b49d86e..a4ad6d5e 100644 --- a/AUTHORS +++ b/AUTHORS @@ -145,31 +145,5 @@ be integrated into your system, and tested, thanks to these people. They have also made their presence known on the mailing list, and can be contacted there. - Debian Jose Carlos Garcia Sogo Fedora Nathanael Noblet - - -Deputies: ---------- - -See DEPUTY for more details on the various roles. - - Compile Checkers - - Devel Distro Testers - - Device Compatibility List Maintainer - - Documentation Page Maintainers - - Downstream Monitors - - External Link Maintainers - - Purity Advisors - - Tech Support Liaison Officers - - Windows World Spies - diff --git a/DEPUTY b/DEPUTY deleted file mode 100644 index a4698e58..00000000 --- a/DEPUTY +++ /dev/null @@ -1,147 +0,0 @@ -From: Chris Frey -Date: Thu, 2 Jul 2009 18:18:32 -0400 -To: barry-devel@lists.sourceforge.net -Subject: Be a Barry Deputy (or, How to volunteer) - -Hi folks, - -I know there are people who want to volunteer, but sometimes don't know -exactly what to do. Sometimes, they know what to do, but they have to -wait on me for some critical architecture. And other times, they do -something, I see their efforts, and then I forget their names in the -future when similar tasks arise. I do my best, but sometimes it is easy -to overlook some facts or details, and it is not meant to be taken -personally. - -As project lead, it is my duty to make volunteering as easy and clear -as possible. And volunteers should be recognized for their work. - -I've come up with a list of roles that people can volunteer for. The idea -behind these roles is that a number of volunteers can be my eyes and -ears in areas that I don't have the time to monitor consistently. -Also, to support the notion that "with many eyes, all bugs are shallow." - -These roles will be added to the end of the AUTHORS file. Each role -can be filled with one or more people, working as a team. They then -report to the mailing list, to keep me up to speed, or to feed patches -or testing data to me. - -I'll add people's names to the AUTHORS file the first time they report -on one of these roles and request to be added to the list. Being on -the list means you intend to continue volunteering for that role. - -Suggestions are welcome. - -- Chris - - - -The List: - -Devel Distro Testers --------------------- - Some distros release very early, and it is possible to follow - along their development cycle. These distros include Fedora, - Ubuntu, and Debian. There have already been some people reporting - bugs on pre-release versions of distros, and that has been very - helpful in ironing out kernel bugs, etc. I'd like to make this - a formal role for those who already live on the bleeding edge. - - These deputies would test the latest stable version and the - git version of Barry on pre-released distros and report any - bugs they find to the mailing list, along with patches if - available, and links to documentation if something new is being - introduced in that distro. - - -Compile Checkers ----------------- - These deputies would simply checkout the latest git tree and - compile everything, on as many machines as they have, and - report any compile errors to the list. This could be - automated as well. - - -Documentation Page Maintainer ------------------------------ - These deputies would claim one page from the web docs or - one man page, and keep it up to date with any changes in - the related program. Sometimes new features in command line - tools such as btool, bjavaloader, etc. get lost in the - cracks, and don't get documented right away in the man page. - These deputies would watch for changes in the program options, - and either submit a patch to the docs, or just a reminder - that we've forgotten something. - - -Downstream Monitors -------------------- - These deputies would watch the downstream distro packager repos - and report any relevant patch and send it to the list. - This is to avoid bugs being fixed in a distro package - but not upstream. - - Not all patches are suitable upstream, but I can easily decide - that if I know about the patches. - - They could also report relevant bugs they see in downstream - bug trackers, and report them to the mailing list. - - And finally, on distros such as Debian stable (when it becomes an - issue), they can submit small maintenance patches for fixes in - upstream that can be used downstream. Examples of such changes - are ppp modem fixes, new chatscripts, or new Product IDs. - - -Windows World Spies -------------------- - These deputies would test every feature on new Blackberry models - and desktop software, and report what can be done with them - that you can't do on the previous model. - - There should be a document listing all these features so - we know what to test against. - - -Tech Support Liaison Officers ------------------------------ - These deputies would camp out on their favourite web forum - (sourceforge tracker included) answering questions, and - repost them on the mailing list if they don't have an answer - themselves. - - -Purity Advisors ---------------- - These deputies would watch for the latest developments in distros - and report if Barry's binary packaging is doing something - that is out of date or deprecated, and how it should be - done better. For example, they could run lintian on Ubuntu, - or report RPM build errors on strict OpenSUSE builds, or - report general directions such as the recent deprecation of HAL. - - -External Link Maintainer ------------------------- - These deputies would maintain a web doc page of external links - of documentation, reverse engineering blogs, and anything - technical related to the Blackberry... and encourage - such links to be posted to the mailing list. If others shared - such links on the mailing list, they would pick them up and - update the documentation. - - -Device Compatibility List -------------------------- - This deputy would maintain a list of Blackberry devies known - to work or not work with Barry. Reports from testers would - be incorporated into a single page summary that would include: - - device model - - version of firmware - - version of Barry - - distro - - what databases are reliable for backup and restore - - what devices charge well - - name of tester, and link to their original mailing list - report - diff --git a/TODO b/TODO index 7f857dc2..46051d9c 100644 --- a/TODO +++ b/TODO @@ -324,3 +324,78 @@ Misc Low Level Todo Items: if ok, remove the sorting code from Contact, Message, and Calendar classes + + + +Other ways to help: +============================================================================== + +Devel Distro Tester +------------------- + Some distros release very early, and it is possible to follow + along their development cycle. These distros include Fedora, + Ubuntu, and Debian. There have already been some people reporting + bugs on pre-release versions of distros, and that has been very + helpful in ironing out kernel bugs, etc. + + To help, build and test the latest stable and git Barry on + whatever distros you have available, and report bugs to the + mailing list. + + +Compile Checker +--------------- + If you have access to cutting edge GCC versions, please submit any + compiler issues you find to the mailing list. + + +Documentation Pages +------------------- + You can help by periodically reviewing the web docs or + man pages, and submit patches or correction notes to the mailing + list. + + +Downstream Monitor +------------------ + Ideally, downstream distro bugs are handled by the individual + package maintainers, but any bugs that are too hard to solve at + the distro level should be passed along upstream. I follow the + Debian package bugs, but other distros could use some help. + + Also, for distro package maintainers, if you have a patch you + apply regularly to Barry, and if it can be incorporated into + upstream Barry, please send your patch to me via the mailing list. + I'd like to keep Barry as up-to-date with such fixes as possible. + + +Windows World Spy +----------------- + To help here, test every feature on new Blackberry models and + official desktop software, and report what can be done with them + that you can't do on the previous model. + + There should be a document listing all these features so + we know what to test against. We can add these features to this + TODO file, or start a new file under doc/ if you like. + + +Tech Support Liaison +-------------------- + There are many web support forums out there, where end users + discuss software and techniques. Unfortunately, I am unable to + follow all these forums, looking for Barry and BlackBerry handheld + related posts. But if you are a member of such a forum, you can + help Barry by responding to such topics, and if appropriate, + forwarding a link to the mailing list, so bugs can be fixed. + + +Purity Advisor +-------------- + Upstream distros tend to change how they do things, or change their + official policies from time to time. If you are a distro user + who keeps up to date with these changes, you can help by + reporting if Barry's binary packaging or software is doing + something that is out of date or deprecated. Even better, please + document how it should be done instead. + -- 2.11.4.GIT