<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
OK, I created a GitHub repo, here:<br>
<br>
<a class="moz-txt-link-freetext" href="https://github.com/wplug/MemberPortal">https://github.com/wplug/MemberPortal</a><br>
<br>
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.<br>
<br>
If anyone else wants to be added, let me know that too.<br>
<br>
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.<br>
<br>
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.<br>
<br>
--Pat.<br>
<br>
<br>
<div class="moz-cite-prefix">On 1/13/2015 12:37 PM, Joe Prostko
wrote:<br>
</div>
<blockquote
cite="mid:CAKfvZxz=g1AG2s2k1WjemuORL=iiZFDuYZ7uyvTxO9=JvgaW+A@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>On Tue, Jan 13, 2015 at 12:21 PM, Pat Barron <<a
moz-do-not-send="true" href="mailto:pat@lectroid.com">pat@lectroid.com</a>>
wrote:<br>
<br>
> 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.<br>
><br>
> 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.<br>
<br>
</div>
Fossil has a built-in bugtracker and wiki, and the timeline
is pretty nice as well. Just go to <a
moz-do-not-send="true" href="http://fossil-scm.org">fossil-scm.org</a>,
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.<br>
<br>
</div>
<div>See here for an example:<br>
<br>
<a moz-do-not-send="true"
href="http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/wiki/home">http://fossil.wanderinghorse.net/repos/libfossil/index.cgi/wiki/home</a><br>
</div>
<div><br>
</div>
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.<br>
<br>
</div>
- joe<br>
<div><br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
wplug-internet mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wplug-internet@wplug.org">wplug-internet@wplug.org</a>
<a class="moz-txt-link-freetext" href="http://www.wplug.org/mailman/listinfo/wplug-internet">http://www.wplug.org/mailman/listinfo/wplug-internet</a>
</pre>
</blockquote>
<br>
</body>
</html>