On Tue, 2009-06-30 at 13:16 +0200, Göran Weinholt wrote: > I don't think I've seen an announcement for this project, so I have a > few questions: > > What is the intent behind the project?
The intent is to organize arbitrary Scheme libraries, which aren't already part of a project, in one place and to provide a place to report and track bugs and questions about these libraries. https://code.launchpad.net/scheme-libraries https://bugs.launchpad.net/scheme-libraries https://answers.launchpad.net/scheme-libraries The purpose of the team is to collaborate on processing bugs and questions and to have the possibility of shared ownership of (commit rights to) branches. > What kind of contributions do you welcome? 1) Any open-source Scheme libraries. Anyone can put branches under the "scheme-libraries" project by registering (or just "push"ing without registering) them under the project, without need for any approval. Read: https://help.launchpad.net/Code/UploadingABranch Register here (or not if you just "push"): https://code.launchpad.net/scheme-libraries/+addbranch You retain exclusive ownership of your branches (unless you make the owner a team). E.g., my branch https://code.launchpad.net/~derick-eddington/scheme-libraries/xitomatl is owned exclusively by me and is under the project. The SRFIs branch https://code.launchpad.net/~scheme-libraries-team/scheme-libraries/srfi is owned by the team and is under the project. If you have an existing branch you'd like to put under the project, you should delete the existing LaunchPad copy of the branch (if there is one) which is not under the project, then optionally register a new branch (probably giving the same name as the old one) under the project, then "push" your same old existing local master copy to the new URL. E.g., for you, Göran, and your cool branch, I believe you can do: $ cd path/to/existing/industria $ bzr push bzr+ssh://[email protected]/~weinholt/scheme-libraries/industria and LaunchPad will automatically register a new branch under the project. (Using SSH the first time makes bzr use SSH thereafter (or so it's seemed for me). You don't have to use SSH, you can use HTTP and omit the user ID from the beginning of the URL. To use SSH, you need to register your public key with your LaunchPad account.) Next, you can delete your old "+junk" copy (it's independent of the new one). 2) Any volunteers to be a bugs/questions coordinator, if you want to help process bug/question reports for branches under the project (review, investigate, assign responsibility, fix, etc.). Currently, the volume of reports is so low that help isn't really needed, but you can still join the team if you just think seeing the reports is interesting. > Will you be making releases (e.g. tarballs)? We won't be making releases of all the branches together. The purpose of the project is only to provide loose organization and loose collaboration. Individuals can make releases of their libraries, and I believe such individualized releases can be listed/organized under the project. For branches which don't do releases (e.g. because they're not stable), it's easy for users to stay up-to-date by "subscribing" to a branch (for new commit notifications) and doing "bzr update". > Is there any coordination between the branches? (My branches are coordinated.) Coordination or collaboration is not at all required. The idea is to provide a liberal place for libraries which otherwise wouldn't have a home or bug reporting or exposure. -- : Derick ----------------------------------------------------------------
