5

Over time, I answered a number of questions here. Many times, these questions were quite (user) specific and answers were created, writing in an improvising way.
In some occasions however, things were definitely more developed into a mature result. Some of these questions/answers furthermore, might be useful to a broader range of users, with a nicely integrated GUI, be maintained, updated and easily available and installable by inexperienced users.

Specifically, I am thinking of combining (some) of these posts into a easily accessible set of workspace tools or whatever the name would be: this one, this one, this one, maybe this, and this one.

Although I love to update these answers every now and then here, like anyone else I have my limitations (won't tell you which :) ), and a one-person team is not the most professional approach to guarantee a long(er) life of a project.

So my question is: how are launchpad teams usually created

EDIT

Narrowing down the question a bit

I get the impression many users of AU, actively involved in developing, are also programmers/developers in their daily live. Their daily environment is more or less related to what they do here.

With me the situation is quite different. Most of my colleagues do not know at all what I am doing here, have little understanding of-, and no affinity with the subject. In other words; my professional network is not related to programming at all.

The most important insight I'd like to gain is if teams (in general) come from existing co operations, brought to Launchpad, or if new teams arise in the virtual world.

Community
  • 1
Jacob Vlijm
  • 85,475

1 Answers1

1

I would flag it, too broad! I lack the experience to cover many aspects. I salute you because you have special finger print on your answers as the those you have mentioned. Those are really prototypes made here as answers.

Free Softwares are built by free community. Large softwares have solid core either one, two or many developers. The core team is generally built in real life (social relations+topic interest) or few virtually (topic interest).

I look to those prototypes as separate projects, each is belongs to you as developer & (OP + Some up voters) as users.

At this point forget about the team, you are the core and you will be so and so as the project get bigger and complicated. Those in the virtual team, they will come & go without a notice, most of them they may never contribute code, at best they will submit a bug.

blaa blaa I can continue talking ... kind of experience resume without much benefits. Try collecting some interest in those projects, and see if it is worthy.

  1. Create a repository on a social git site, popular one MR. Octopus GitHub.
  2. Update your answer and a link to your new upstream project (keep original code)
  3. Create a mirror project on Launchpad.
  4. Prepare Debian packaging
  5. Publish a PPA
  6. Update your answer again and add another link to PPA.

So now basically you have upstream project development on GitHub & binary releases on Launchpad. After this, Que Sera, Sera (Whatever Will Be, Will Be). I just wish you best luck :D.

I have a answer here that I promoted it to a very verytiny projecto.

Time for another Ads ;)

Btw, If you are trying to make a handover that's will not work. People care only about what they really need and they evaluate it how it's worth before they put some time in it.

user.dz
  • 49,176