[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-register-public] [task #6535] Submission of Public Event Manag
[Savannah-register-public] [task #6535] Submission of Public Event Manager System
Fri, 16 Mar 2007 22:13:43 +0000
Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:18.104.22.168) Gecko/20060911 SUSE/22.214.171.124-0.2 Firefox/126.96.36.199
Follow-up Comment #1, task #6535 (project administration):
Follow-up Comment #1:
SW> I'm evaluating the project you submitted for approval in Savannah.
SW> At first, please include a (perhaps temporary) URL pointing to the source
*The project hasn't yet started and has no code yet*
SW> If you are still concerned with privacy, however, you can forward the
code to me by email.
*no privacy concerns. it's an open project*
SW> We wish to review your source code, even if it is not functional, to
catch potential legal issues early. For example, to release your program
properly under the GPL you must include a copyright notice and
permission-to-copy statements at the beginning of every file of source code.
This is explained in http://www.gnu.org/licenses/gpl-howto.html. Our review
would help catch potential omissions such as these.
* I read the policy before posting the project and it's OK to me. Since the
coding hasn't yet started you'll be able to monitor the code from the very
SW> If you haven't got any source code to show us,
SW> ...why do you need the project-registration _now_?
*It's not that I _need_ it. I just think it is a good practice to start at
the right place to avoid later migrations (they use to cause trouble in the
code's integrity and among the team members, either because it is anoying to
re-learn procedures and/or because some might not like GNU's policies. I find
it beter and more straight forward to start here from the beginning)*
SW> Which services do you would like to use on Savannah?
- The call for help pages
- The version control (even for development documents, wich I regard as
tools, just like a make script).
- Task tracker
- Mailing lists
SW> How can we help you?
1.- Letting me know if there's already an alternative to my project there. I
see no sense in duplicated efforts and I would join the other one instead.
2.- Helping me envolve more people
3.- Providing advice
SW> At second, your project is not yet part of the GNU project, so we cannot
accept its current name. While there are non-GNU programs with names that
include 'gnu', such as gnuplot and gnuboy, they are not hosted on Savannah.
We want to maintain the distinction between GNU and non-GNU projects.
*That's OK. I'd prefer to start being a GNU one. What else is needed for
In any case, there's no problem in removing the "G"/"GNU" to PEMS (Public
But I think I'm not able to change it once submitted but not yet approved,
SW> When your project is accepted into the GNU project you may change its
name. You can do this by asking us.
*How do I change the name _now_ to get rid of thw "G"?*
SW> At third, your project is not part of the GNU project, so we cannot
accept its current type.
*Same as before. I prefer to be GNU, but no problem in having it changed. I
just don't find how to do it.*
SW> At fourth, we need a detailed technical description that specifies such
requirements as programming languages and ***external libraries***. It should
be at least one-half a page.
Not specified yet. It will probably depend on the developers that I manage to
envolve in this. The project's description describes my (top level) intentions
regarding such issues (multi-plattform, standards compliant, GNU compatible,
...a.s.o.). The "except" is a bug, it should read: "expect".
Reply to this item at:
Message sent via/by Savannah