[wplug-internet] Membership Database design

John Lewis oflameo2 at gmail.com
Tue Jan 13 15:11:55 EST 2015


Is the account tied to a WPLUG email account? If it is not we are going
to have the exact same problems very other time we had someone make an
account for WPLUG. Is the account documented on the WPLUG VPS?

I don't have a GitHub account yet because I don't it tied to my Google
account and I am still trying to configure dovecot on my VPS so  I have
my own private mail server so I will be the first one to read my emails
and not Google.

I already have a working ldap server so I want to get it tied in
properly while not multiplying the number of maildir directories needlessly.

I like copyleft licenses myself, but I don't care with this project.

On 01/13/2015 02:39 PM, Pat Barron wrote:
> OK, I created a GitHub repo, here:
> 
> https://github.com/wplug/MemberPortal
> 
> I added myself and Joe as collaborators.  John, I didn't find a GitHub
> account for you.  If you have a GitHub account, let me know, and I will
> add you.
> 
> If anyone else wants to be added, let me know that too.
> 
> I set this repo up to use the Apache 2.0 license (i.e., I personally
> don't particularly care for "copyleft"...).  If there's a good argument
> to use some license, I can always delete the repo and start over.
> 
> I'll open some issues in GitHub against this repo, with the items that
> were previously mentioned.  Assuming we're good with the license and
> all, I'd suggest that further traffic on this project be handled through
> the Issues tab in the repo itself.
> 
> --Pat.
> 
> 
> On 1/13/2015 12:37 PM, Joe Prostko wrote:
>> On Tue, Jan 13, 2015 at 12:21 PM, Pat Barron <pat at lectroid.com
>> <mailto:pat at lectroid.com>> wrote:
>>
>> > I think the easiest way to proceed from here is to set up a GitHub
>> repository, and that way we can use the Issues system in GitHub to
>> track the open work (and who is doing it), and we can keep all that
>> traffic off this mailing list.  It also opens up potential
>> participation to people who aren't on the mailing list.
>> >
>> > Alternatively, we could use something like Fossil, and tie it into a
>> system like TRAC (does TRAC have a Fossil plugin?) and host it
>> ourselves.  But as distasteful as Git can be, I think there's more
>> "critical mass" in terms of people who are familiar with it.  I'll be
>> happy to set up that repo (and we can start by putting the
>> requirements doc in there) if we want.
>>
>> Fossil has a built-in bugtracker and wiki, and the timeline is pretty
>> nice as well.  Just go to fossil-scm.org <http://fossil-scm.org>, as
>> it is a running instance of Fossil itself (except for the Downloads
>> page).  Yes, out of the box it's not the prettiest thing ever, but it
>> can be themed if need be.
>>
>> See here for an example:
>>
>> http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/wiki/home
>>
>> That all said, probably everybody who isn't me is more comfortable
>> with Git and Github, and that is fine, so I have no problems using it
>> whatsoever.  Obviously I don't want us to get into a big debate about
>> what VCS and collaboration platform to use, so if you want to set up
>> something on Github, Pat, feel free.
>>
>> - joe
>>
>>
>>
>> _______________________________________________
>> wplug-internet mailing list
>> wplug-internet at wplug.org
>> http://www.wplug.org/mailman/listinfo/wplug-internet
> 
> 
> 
> _______________________________________________
> wplug-internet mailing list
> wplug-internet at wplug.org
> http://www.wplug.org/mailman/listinfo/wplug-internet
> 



More information about the wplug-internet mailing list