Difference between revisions of "Gna!"

From Archiveteam
Jump to navigation Jump to search
(rm example export link since I forgot it's admin-private)
(more on trackers)
Line 19: Line 19:
** There's also a ViewVC web front-end to browse code.
** There's also a ViewVC web front-end to browse code.
* '''Ticket tracking'''
* '''Ticket tracking'''
** Project admins (only) can set up XML export of their own issue text/metadata ("Export" item on tracker admin menu).
** Up to 4 trackers per project: 'bugs', 'patch', 'task', 'support'
** Project admins (only) can set up XML export of their own ticket text/metadata ("Export" item on tracker admin menu).
*** Only option for third parties looks like web scraping.
** There's no supported interface for grabbing issue attachments (such as patches) even for project admins though.
** There's no supported interface for grabbing issue attachments (such as patches) even for project admins though.
*** Attached files are allocated global increasing integer IDs, e.g. [https://gna.org/bugs/download.php?file_id=29845 file #29845]. It's probably possible to scrape all public files that way.
*** Attached files are allocated global increasing integer IDs, e.g. [https://gna.org/bugs/download.php?file_id=29845 file #29845]. It's probably possible to scrape all public files by varying 'bugs' and the ID.
** Only option for third parties looks like web scraping.
** Individual tickets can be private. (Maybe files too?)
** Individual tickets can be private.
* '''File hosting''' at http://download.gna.org/
* '''File hosting''' at http://download.gna.org/
* '''Project websites'''
* '''Project websites''' on home.gna.org
** e.g. http://home.gna.org/freeciv/
** These are managed via Subversion [https://gna.org/cookbook/?func=detailitem&item_id=107], so grabbing svn by rsync as above should also save website data + history
** These are managed via Subversion [https://gna.org/cookbook/?func=detailitem&item_id=107], so grabbing svn by rsync as above should also save website data + history
* '''Project documentation''': FIXME
* '''Project documentation''': FIXME

Revision as of 13:34, 25 February 2017

Gna!
URL http://www.gna.org
Status Closing
Archiving status In progress...
Archiving type Unknown
IRC channel #gnarm (on hackint)

Gna! is a centralized location where software developers can develop, distribute and maintain free (GPL-compatible) software. It is an instance of the Savane code-hosting platform[1].

Hosted data

As of 2017-02 it claimed to have 1458 hosted projects. (Many are probably abandoned and will not be saved by their project admins before shutdown.)

  • Code hosting using CVS, Subversion, and (apparently) Arch
    • All subversion repos available via anonymous rsync: rsync://svn.gna.org/svn/ (ref: bottom of every project's svn page e.g. [1])
    • Ditto CVS, it looks like: rsync://svn.gna.org/cvs/
    • FIXME: what about Arch/tla? [2]
    • There's also a ViewVC web front-end to browse code.
  • Ticket tracking
    • Up to 4 trackers per project: 'bugs', 'patch', 'task', 'support'
    • Project admins (only) can set up XML export of their own ticket text/metadata ("Export" item on tracker admin menu).
      • Only option for third parties looks like web scraping.
    • There's no supported interface for grabbing issue attachments (such as patches) even for project admins though.
      • Attached files are allocated global increasing integer IDs, e.g. file #29845. It's probably possible to scrape all public files by varying 'bugs' and the ID.
    • Individual tickets can be private. (Maybe files too?)
  • File hosting at http://download.gna.org/
  • Project websites on home.gna.org
  • Project documentation: FIXME
  • Mailing lists using Mailman
    • Which means public archives are available in mbox format (albeit with email addresses mangled). e.g. [4]
    • Some mailing lists are private.
  • Project metadata: groups, users, news etc. Probably only available via web scraping.
  • Usage stats at http://stats.gna.org/

Shutdown Notice

  • A pending shutdown was first announced in Nov 2016[2]
  • A news item was posted to the front page 2017-01-31 linking to the above.
  • Exact shutdown timeline is currently (2017-02) unclear.