PLD Linux distro registration

Forgot to add:

PLD currently has two main lines of development:

* PLD Ac 2.0 - stable, maintained by Elan "Glen" Ruusamäe reachable at glen@pld-linux...
* PLD Th 3.0 - in active development, maintained by Arkadiusz "arekm" Miśkiewicz reachable at arekm@pld-linux...

If you need an "official" confirmation these are the guys to contact. We are a community project and currently there is no formal organization in place.

i prefer to be called glen in all-lower-case :)

Can we get a reply from one of the admins?

I'll get this done today.

Thanks a lot, let us know if you need more information :)

Can you create a team to hold your official members and give me its URL?

https://edge.launchpad.net/~pld-linux

Done: https://edge.launchpad.net/pld-linux/

Thanks. We still can't access the bug tracker nor the blueprints feature (bugs says we don't use them and enabling blueprints in distro details results in a "forbidden" error). Is there an official bugzilla migration path? We'd like to move all bugs from https://bugs.pld-linux.org/ and point future reporters here.

Okay, I'll enable them for you -- apparently I can!

Ah, as for the Bugzilla migration path, we do have a script that imports from it. I'll need to forward your request to James Henstridge who can advise on this.

I'd also love to hear how distroseries work. Documentation mentions them being under the actions menu but I can't see them there. We'd like to create at least 3 series (PLD Ac, PLD Th and PLD Titanium).

Also - can we track bugs in packages that are not uploaded to Launchpad? We are an RPM-based distro so we keep a separate infrastructure for packages.

Thanks Christian Reis, that solved my question.

Oops, misclicked, sorry.

I'll close this for now and open separate requests for remaining issues. Thanks for your help.

You asked:

  Also - can we track bugs in packages that are not uploaded to Launchpad? We are an RPM-based distro so we keep a separate infrastructure for packages.

That's a really good question. Right now, you can't, though we could do a mass-inclusion of package names to allow you to manage bugs properly. I believe there's a bug filed for a better way of doing this, but it's been hard to prioritize up to now. If you want it to be a priority, please remind https://edge.launchpad.net/~julian-edwards and https://edge.launchpad.net/~bjornt during the month of July to ensure he estimates how much Soyuz effort it will be in our planning cycle.

I think having to import package names on a regular basis could be a bit problematic for a big distribution. It would be easier if we could just select "allow any package name" in distro details and then it would be up to the bug squad to make sure the package field contains a proper value. Please see https://bugs.edge.launchpad.net/launchpad/+bug/226982 for a proposal.

Cool. Anything we can do to close this question?

I think we can move to the bug report and continue there,

.