[Savannah-register-public] [task #14971] Submission of EmacsConf

[Ineiev]

Follow-up Comment #7, task #14971 (project administration):

> Aside from a mailing list, we need infra to host a wiki on emacsconf.org
(not sure if it can be handled using regular cvs web repos),

Savannah generally doesn't provide wiki, all people get is cvs web.

> ability to create git repositories on savannah,

New Git repositories are added to projects by Savannah admins on request from
packages.

> mediagoblin instance for hosting conference videos and media (similar to
that of LibrePlanet), and also integrating with civicrm's event module and
trustcommerce for handling RSVPing and purchase of tickets for the
conference.

I think Savannah can't help with these (maybe sysadm...@fsf.org?).

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

[Savannah-register-public] [task #14528] Submission of relax

[Ineiev]

Follow-up Comment #33, task #14528 (project administration):

>> ...but anyway, when the user looks at these PDB files...
> There is a README file in the same directory that lists the files as being
in the public domain.

These are text files (as well as AUTHORS), they should include the notices.
README is only a fallback for binary files.

WRT the GFDL, I'm not sure. Perhaps you'll have to speak to licens...@fsf.org.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

[Savannah-register-public] [task #14971] Submission of EmacsConf

[Amin Bandali]

Follow-up Comment #6, task #14971 (project administration):

>  Then perhaps "www.gnu.org portion" would be a more adequate type; but
you'll have to speak to FSF's people like rms (not sysadmins) to approve it.

That makes sense.  I'll wait to hear from sysadmin@, then I'll ask them to
kindly put me in touch with the right people at FSF, if not rms himself.

>  Please note https://www.gnu.org/philosophy/words-to-avoid.html#Content

Thanks for linking that.  I had no idea that "content" was one of those
words.

> Anyway, it would help if you describe your needs in more detail: what you
are going to host, what facilities you will need and how you plan to use
them.

My apologies if I wasn't clear enough.  I've included below a copy of the
email I sent to sysadmin@ last night, which contains some more details about
our current infra and what we'd need.

> Do you actually need a dedicated Savannah group? Can't you use, say,
https://savannah.gnu.org/p/emacs ?

Hmm, that may be a possibility.  Aside from a mailing list, we need infra to
host a wiki on emacsconf.org (not sure if it can be handled using regular cvs
web repos), ability to create git repositories on savannah, mediagoblin
instance for hosting conference videos and media (similar to that of
LibrePlanet), and also integrating with civicrm's event module and
trustcommerce for handling RSVPing and purchase of tickets for the conference.
 At least that's what I can remember right now.  I'll amend more to the list
if anything comes up.



Amin Bandali  (Today 01:58) (sent)
Subject: Hosting for EmacsConf on Savannah and GNU infra
To: sysad...@gnu.org
Date: Sat, 23 Jun 2018 01:58:40 -0400

Hello there,

I'm one of the organizers of the previous EmacsConf back in 2015.
I just submitted an application for getting EmacsConf set up on
Savannah: https://savannah.gnu.org/task/?14971
I selected 'GUG' as project type because that seemed the closest.

Our current infrastructure was down for a while, but I got it
back up and running again over the course of last few days.
However, I'd love to be able to host various parts of the
EmacsConf infra on Savannah and other GNU infra, for a few
reasons:

. As a way of showing that EmacsConf values and very much agrees
  with the philosophy of the GNU project and FSF,
. to hopefully bring more eyes on Savannah and free software
  tools, and
. also avoid incurring the cost of running our own infra while we
  could rely on that of GNU.

Currently, various pieces of emacsconf.org are as follows:

. emacsconf.orgthe front page and the wiki of the site
. git.emacsconf.orgself-hosted git server (using Gogs)
. discourse.emacsconf.org  discussion forums

- For the main site, emacsconf.org, I'd like to transition from
  the current Django-based CMS to using a wiki, perhaps either
  DokuWiki or Oddmuse, both of which are free software.
- For our git repos, I'd like to host them on savannah.gnu.
- For our discussion forum, I'd like to use a traditional mailing
  list over on lists.gnu.org.

Additionally, it would be wonderful if FSF could help

- set up mediagoblin for us, so we could host the conference
  videos and media on media.emacsconf.org, like LibrePlanet, and
- provide some info on how to integrate civicrm's civi event
  module into our website so as to have a way of letting people
  RSVP for the conference, and also about using trustcommerce for
  handling ticket payments.

Lastly, we have the #emacsconf irc channel on freenode, which is
already listed among the official channels on
https://www.gnu.org/server/irc-rules.en.html, so there's nothing
more to be done on that front.

Thanks very much in advance for the help.

Best,
-amin


___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

[Savannah-register-public] [task #14971] Submission of EmacsConf

[Ineiev]

Follow-up Comment #5, task #14971 (project administration):

> 1. Would that mean the mailing list etc would be on the nongnu.org Savannah
instead of gnu.org? I think that'd be a bit unfortunate, since e.g. our irc
channel is already "official", and ideally we'd be able to have that
throughout.

Then perhaps "www.gnu.org portion" would be a more adequate type; but you'll
have to speak to FSF's people like rms (not sysadmins) to approve it.

> I mean, we won't be using a CMS anymore,

Please note https://www.gnu.org/philosophy/words-to-avoid.html#Content

Anyway, it would help if you describe your needs in more detail: what you are
going to host, what facilities you will need and how you plan to use them.

Do you actually need a dedicated Savannah group? Can't you use, say,
https://savannah.gnu.org/p/emacs ?

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

[Savannah-register-public] [task #14971] Submission of EmacsConf

[Amin Bandali]

Follow-up Comment #4, task #14971 (project administration):

>  Change the group type to "non-GNU software and documentation".

Hmm, two things:

1. Would that mean the mailing list etc would be on the nongnu.org Savannah
instead of gnu.org?  I think that'd be a bit unfortunate, since e.g. our irc
channel is already "official", and ideally we'd be able to have that
throughout.

2. I don't see any options to change the type from my end.  If we were to do
that, it'd likely have to be by a Savannah admin.

>  Realistically, you can use git if you setup a Git-to-CVS gateway (no,
Savannah sysadmins are not likely to help you with that).

Cool, thanks, good to know.

> Then we'll have to wait for at least first drafts of your new version in
order to evaluate it.

Is there much to be evaluated in this case though?  I mean, we won't be using
a CMS anymore, and will be switching to a DokuWiki or Oddmuse, both of which
are free software.  As for the actual content, it likely wouldn't be much
different from what's already up on emacsconf.org, except we'll be adding the
planning notes etc for the next conference as we work them out.

So instead of setting up the new wiki and then migrating it, I thought I'd
wait until we migrate over, then set up the wiki.  But if you say so, I don't
mind doing it beforehand and setting up on our current infra.


On a side note, after posting this submission here last night I also emailed
sysad...@gnu.org, elaborating a bit on the points that didn't really fit on
the application form.  I wonder if the FSF sysadmins or any of the other staff
would have anything to add or chime in.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

[Savannah-register-public] [task #14951] Submission of hcj-js

[Ineiev]

Update of task #14951 (project administration):

  Status: In Progress => Cancelled  
 Open/Closed:Open => Closed 


___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

[Savannah-register-public] [task #14952] Submission of bitfield

[Ineiev]

Follow-up Comment #2, task #14952 (project administration):

If there is no further interest, I'll cancel this submission.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

[Savannah-register-public] [task #14954] Submission of Alette

[Ineiev]

Follow-up Comment #2, task #14954 (project administration):

If there are no further interest, I'll cancel this submission.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

[Savannah-register-public] [task #14959] Submission of emacs-doc-emacs-ja

[Ineiev]

Update of task #14959 (project administration):

  Status: In Progress => Cancelled  
 Open/Closed:Open => Closed 

___

Follow-up Comment #4:

No response; cancelling.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

[Savannah-register-public] [task #14971] Submission of EmacsConf

[Ineiev]

Follow-up Comment #3, task #14971 (project administration):

> What are the alternatives, if I'd like to have those features? 

Change the group type to "non-GNU software and documentation".

> Another question: for the web repositories, is using CVS mandatory, or can
git be used as well?

Realistically, you can use git if you setup a Git-to-CVS gateway (no, Savannah
sysadmins are not likely to help you with that).

> If CVS is mandatory, are there any plans for extending the system to allow
git there too?

Yes, but they are not likely to be implemented any time soon.

You know my personal opinion: CVS fits websites better than Git.

> we'll completely revamp the website... no copyright notices or license
headers were added to individual files

Then we'll have to wait for at least first drafts of your new version in order
to evaluate it.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

[Savannah-register-public] [task #14971] Submission of EmacsConf

[Amin Bandali]

Follow-up Comment #2, task #14971 (project administration):

I chose GUG because that seemed like the closest thing to EmacsConf from that
list.

What are the alternatives, if I'd like to have those features?

Another question: for the web repositories, is using CVS mandatory, or can git
be used as well?  If CVS is mandatory, are there any plans for extending the
system to allow git there too?

-amin

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

[Savannah-register-public] [task #14949] Submission of ctbankix-continuation

[Ineiev]

Follow-up Comment #3, task #14949 (project administration):

We discourage simplistic one-file projects: they don't need a full-fledged
Savannah group and can instead be "hosted" on a single web page; besides that,
it is based on a distro that isn't fully free, that's an issue as well.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

[Savannah-register-public] [task #14966] Submission of useful-wiki

[Robin Wils]

Follow-up Comment #4, task #14966 (project administration):

I taught that all projects were allowed.
Sorry for misunderstanding the type of hosting.

I won't submit sites anymore, 
thanks for letting me know!

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

[Savannah-register-public] [task #14968] Submission of Gentooza's Sudokus Resolver

[Ineiev]

Follow-up Comment #3, task #14968 (project administration):

Please remove backup files created by your editor from your tarball, this
looks impolite.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

[Savannah-register-public] [task #14966] Submission of useful-wiki

[Ineiev]

Follow-up Comment #3, task #14966 (project administration):

There is a problem. We don't host websites on Savannah. We host software,
documentation, user groups.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/

[Savannah-register-public] [task #14966] Submission of useful-wiki

[Robin Wils]

Follow-up Comment #2, task #14966 (project administration):

Thanks a lot for the useful feedback!
I tried to update some things. I wrote some of the back-end and found python a
better option as java so I went with python.
Python is going to be the back-end so the languages that the project will use
will not change anymore.
I also have better info about which dependencies that the project will use.
The project won't need more dependencies than the listed ones.



*DESCRIPTION:*
*Project details*
This project is a website. 

The purpose of this project is to help people with finding the right wiki's
quickly. People will be able to add wiki's,
they will also have to add some tags to the wiki so that people can find the
right wiki's easily.
This project will use mongodb as database.

*Requesting wikis and tags*
Everyone will be able to request a wiki to the site,
which someone (currently me) will have to accept by clicking a link in their
email. 
The link is just to get rid of wrong wikis and to get rid of spammers.
The same thing happens for requesting new tags. 

*Searching wikis*
The homepage of the site will contain a table with wikis.
People will be able to filter the wikis based on the wiki-tags and
wiki-names.
   
   
*OTHER SOFTWARE REQUIRED:*
*Dependencies*
* Python 3.7   | (?Has their own License?, GPL-Compatible) | Python
3.7_website 

* Python3-flask| (BSD License, GPL-Compatible | Python3-flask_website


* (pip) pymongo| (Apache License 2.0, GPL-Compatible) | pymongo_website
, license location


* (pip) Flask-Mail | (BSD License, GPL-Compatible) | Flask-Mail_website
, license location



___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/