Greetings from the Great White North (in my case, Grande Prairie, Alberta, Canada).
5 weeks or so ago, it seemed reasonable to start doing something with a bunch of code that I have. Some finished, some almost, some hardly started. While I've known of versioning systems for decades, I've never actually spent any significant time working with any particular one. They all have rules, and one has to work with what is allowed. Where I am starting from, is a GIS (you could call it geostatistics, I see it as also being useful to working with surface chemistry or scanning tunneling microscopy, atomic force microscopy, and others) project I started on. I have about 30 Perl modules built, I am guessing to finish it is probably another 15. If things ever go to CPAN, they would like useful hierarchies of names. And so I have attempted to name these things in that manner, and they are all over the ballpark. To me, this is all one big project. And while I could split every piece into its own domain, it might be useful to keep everything together too. Looking at the Git world, what seems to work as the "one big project" is subtrees. But Debian does not have subtree support. I wrote the maintainers, but after doing so I ran across a bugreport about subtrees at Debian, so I don't expect a reply. I don't know if subtrees would work, to me it just looks like they might. How people talk about subtrees versus submodules (which is in Debian Git), submodules wouldn't work. Sure, I can download git from source and compile it for myself, and ditch the Debian Git that is now here. Are git subtrees something to use, or is this a partial answer looking for a better approach, and that is why Debian is dragging its feet at putting it in Debian Git? I run across 3 different versions of git subtrees. One complaint was lack of documentation (which seems to be a constant in software). If that makes the most sense here (my home server), does that impact projects at nongnu? I think it would be really nice, if someone could put together a "Hello World" tarball which represents the website side of a Savannah project. Looking around, I haven't a clue as to how to set this CVS side up, and I will have to wait until I actually have an approved project to start. I have autism, I can appreciate being pedantic. :-) Licenses are a necessary evil. I'm a dinosaur, I live in an 80 column wide world in emacs. It might be nice to have copies of the various licenses for that format. Maybe you could give them the extension ".vt52"? In any event, I have just about finished reformatting my .vt52 versions of GPL2, Artistic2 and FDL, which it seems I need to include verbatim. I need to go through all my files, and point to the appropriate license in all of them. And then I guess I can apply for a project. Which gives people here some time, to answer questions here, and I'll know whether I am dealing with 1 project or many. Have a great day! Gord
