Links to Alexandria related repos?

17 views
Skip to first unread message

aiscott

unread,
Feb 27, 2012, 7:34:41 PM2/27/12
to prj-ale...@googlegroups.com
So I'm not a software developer by profession; I'm in hardware.  Our usage of VCS is quite a bit behind the times, and so I'm not too familiar with git/github etiquette.  

I'm sure we're all going to have our own hackish tools that we use to start hashing things out on this project.  I think it would be great if we exposed these tools, incomplete and hackish as they may be, to the benefit of each other.  I was thinking that we'd all have peripheral Alexandria related repos, and if that is the case, perhaps a link to those repos in the main Alexandria-project readme would be good?

Or would it be better/more appropriate to have something like a dev-tools sub directory in the main repo, and we put our "figuring things out" tools in there?  That doesn't seem as appealing to me, but I'm fine with whatever.  I just would like to see what we all have available, no matter how incomplete/hackish/ugly or whatever.

Am I way off base?  What do you all think?

--Scott

Daniel King

unread,
Feb 27, 2012, 7:44:26 PM2/27/12
to prj-ale...@googlegroups.com
On Mon, Feb 27, 2012 at 19:34, aiscott <ephe...@gmail.com> wrote:
> Or would it be better/more appropriate to have something like a dev-tools
> sub directory in the main repo, and we put our "figuring things out" tools
> in there?  That doesn't seem as appealing to me, but I'm fine with whatever.
>  I just would like to see what we all have available, no matter how
> incomplete/hackish/ugly or whatever.

My first thought would be to have a "dev-tools" repo which individual
contributors could fork and vc their tools in. If a tool became widely
used, it could be merged into the primary branch. Using this
structuring of repos, GitHub will automatically keep track of the
fork'ed repos for us.

Maybe this isn't quite right though if the forked repos will vary
wildly from the original one. Maybe the best bet would be to have a PA
organization on github and then you could access the individual
developers' pages directly.

--
Dan King
College of Computer and Information Science
Northeastern University

Brian Troutwine

unread,
Feb 27, 2012, 9:29:50 PM2/27/12
to prj-ale...@googlegroups.com
On Mon, Feb 27, 2012 at 7:34 PM, aiscott <ephe...@gmail.com> wrote:
> So I'm not a software developer by profession; I'm in hardware.  Our usage
> of VCS is quite a bit behind the times, and so I'm not too familiar with
> git/github etiquette.
>
> I'm sure we're all going to have our own hackish tools that we use to start
> hashing things out on this project.  I think it would be great if we exposed
> these tools, incomplete and hackish as they may be, to the benefit of each
> other.  I was thinking that we'd all have peripheral Alexandria related
> repos, and if that is the case, perhaps a link to those repos in the main
> Alexandria-project readme would be good?

Absolutely. We're all going to be flinging spaghetti at the walls;
eventually something will stick and at that point we can think about
higher level organization.

> Or would it be better/more appropriate to have something like a dev-tools
> sub directory in the main repo, and we put our "figuring things out" tools
> in there?  That doesn't seem as appealing to me, but I'm fine with whatever.
>  I just would like to see what we all have available, no matter how
> incomplete/hackish/ugly or whatever.
>
> Am I way off base?  What do you all think?

Produce, announce to the list and if something comes along well enough
to be exciting go from there.

> --Scott

--
Brian L. Troutwine

Reply all
Reply to author
Forward
0 new messages