taskSavannah Administration - Tasks: task #6535, Submission of Public Event Manager...

 
 

task #6535: Submission of Public Event Manager System

Submitter:  Igor Zubiaurre <fioddor>
Submitted:  Sun 18 Feb 2007 03:42:48 PM UTC
   
 
Should Start On:  Sun 18 Feb 2007 12:00:00 AM UTC Should be Finished on:  Wed 28 Feb 2007 12:00:00 AM UTC
Category:  Project Approval Priority:  * 5 - Normal
Status:  Cancelled Privacy:  Public
Assigned to:  Beuc Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Sun 08 Apr 2007 01:25:13 PM UTC, comment #2: 

Hi,

To be part of the GNU project, please check the GNU Evaluation process, outlined at:
http://www.gnu.org/help/evaluation.html

Currently we don't have the ressources to accept project without source code and check it as it progresses, so I have to close this submission for now. Feel free to resubmit once your project starts.

Regards.

Sylvain Beucler <Beuc>
Fri 16 Mar 2007 10:13:42 PM UTC, comment #1: 

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 code.

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 beginning*


SW> If you haven't got any source code to show us,

That's right!

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 that?
In any case, there's no problem in removing the "G"/"GNU" to PEMS (Public Event Manager).
But I think I'm not able to change it once submitted but not yet approved, right?*

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".


Igor Zubiaurre <fioddor>
Sun 18 Feb 2007 03:42:48 PM UTC, original submission:  

A new project has been registered at Savannah
This project account will remain inactive until a site admin approves or discards the registration.


Registration Administration


While this item will be useful to track the registration process, approving or discarding the registration must be done using the specific Group Administration page, accessible only to site administrators, effectively logged as site administrators (superuser):



Registration Details


  • Name: Public Event Manager System
  • System Name:  pems
  • Type: Official GNU software
  • License: GNU General Public License V2 or later





Description:

Project unix name (suggested): GEMS (or G-PEMS)
Full Project name (suggested): GNU (Public) Event Management System
Project type: Software
SW License: GPL for the modules created within the project (version to be discussed among team members). Some modules with other GPL-compatible licenses might be used and/or modified.

The project aims to develop a free software application to help organisations organise and manage public events.


Conceptual model


It should someday cover following top level functionalities:

  • Several resources repositories:

  - speeches
  - speakers
  - sites (auditoriums)

  • Event organisation information
  • Financing & Sponsor management
  • Marketing management
  • Event/speeches requests
  • Integration with other compatible event-management and/or event tracking systems



Physical Model


The system would need
- an underlying database
- a functional system to manage workflows, alerts, etc
- several front ends for different pourposes

There's no source code yet. Not even a programmer. The intention is to start the project writing high level conceptual and technical specifications (vision, stakeholders and needs, functional requirements, system requirements, use case descriptions, ...) while gathering help to create the software itself. Then create ASAP a tiny basic core-functional version and then extend it according to a roadman.

In order to apply the unix-like philosophy of strong modularity based on small versatile modules, some modules might spin-off as separate projects if found reusable for other pourposes.





Other Software Required:

The physical model is not yet developed and might depend on the team members' taste. I'd like the system to remain as standard as possible to avoid strong dependencies, which, by the way, I don't except in such a classic management software (no strage cutting edge artifacts needed, its added value relies in top level functional aspects, not it low level technical ones). If unavoidable, it should at least be from a free software.

The underlying database, for example, should just be SQL compliant (maybe not necessarily 100%, but best if so).


Other Comments:

I've searched for such an application and found nothing, but maybe they passed unseen to me. If so, please, let me know and I'll check them first to see if they fit my plans and I can avoid a duplicated effort.



Igor Zubiaurre <fioddor>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by Beuc (Posted a comment)
  • -email is unavailable- added by fioddor (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2007-04-08 Beuc StatusNone Cancelled
        Assigned toNone Beuc
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code