Requesting project group "zearin-libs"

Asked by Zearin

I'd like to start a project group, which I would like to organize into subprojects under a single group. Each subproject would build on files contained in the main group; that way I don't have to create a new bug record in each project because of a bug in shared code.

Question information

English Edit question
Launchpad itself Edit question
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Launchpad Janitor (janitor) said :

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Christian Reis (kiko) said :

Oops, sorry for not getting to this one. So two things:

  - Can I have URLs to the projects that will be inside this project group?
  - Can I have the URL to the project group's homepage on the web?

Revision history for this message
Zearin (zearin) said :

Eep! Now I'm guilty of getting to this one slowly.

Actually I haven't created the other projects yet. I was loathe to do so under SourceForge, and it was Launchpad that inspired me to actually turn this fuzzy idea I had into a real project. So, there aren't any other URLs for you, except for the single project I've made thus far:

So, since you are asking for these up front, does that mean that I would be unable to create a group first and then add subprojects as I start them? (If this is possible, this would be the ideal. :)


Revision history for this message
Christian Reis (kiko) said :

No, it's fine -- it's just because I like to know a bit more about project groups before they're created. I try to avoid creating groups for inactive projects, too. What I recommend is that you get started on your individual projects and when you have some deliverables out there I'll be happy to create a project group for you. How does that sound?

Revision history for this message
Zearin (zearin) said :

Thanks for the explanation!

Yep, that's okay with me. Makes sense, too, as I'm juggling this with school so progress may be stop & go for a while.

Not that it's my intention to drag this out, but regarding that “when you have some deliverables out there”—I'm pretty new at participating in open source, so my work has always kind of been devoid of any defined “deliverables”. I'm not sure how to go about working towards a deliverable as opposed to just random coding here and there. In fact, it's my desire to get some organization to this chaotic work method that is a *big* part of why I'm moving this work to Launchpad.

So, basically, I guess what I'm asking is how to go about putting out a deliverable if you've never done it before.

(1) Do you have any advice along these lines?

(2) I'm not sure exactly how Launchpad's deliverables work, but if I understand correctly they appear to be Ubuntu-only. Is this correct?

Revision history for this message
Christian Reis (kiko) said :

Well, one deliverable is a branch with source code -- if you have one of those that isn't empty and is reasonably active I'd count it as a "deliverable".

Open source projects also do releases every once in a while, where a release is almost always a tarball with a version number. Launchpad can host these files as downloads -- just add a release to your trunk series and upload files to it when you are ready.

You can also build Ubuntu packages of your project. Most projects make packages of their releases, but you can also build packages of snapshots of your trunk branch. Read about PPAs on to understand more about our packaging service -- in fact, contains information on branches and releases too. Let me know if you have any other questions, I'm glad to help out.

Can you help with this problem?

Provide an answer of your own, or ask Zearin for more information if necessary.

To post a message you must log in.