On segunda-feira, 4 de novembro de 2013 12:14:15, Philippe Coval wrote: > Since there is a will to open tizen maintenance to all contributors. > I am candidate to test this process, > (I am unaware tizen.org has external maintainers yet, are there ?) > > So, Please tell, > How a developer can apply for (co-)maintenance of an existing project ?
Hello Philippe The idea is that there should be exactly one official maintainer per component (where a component can be one or multiple Git repositories). This maintainer has the duty to keep the the code working and in healthy condition. So we can't offer you maintenance of an existing project that already has a maintainer. Here's what we can use you in: a) be a maintainer in a component that has no maintainer b) be a maintainer in a new component that you're importing into Tizen (that's the case for Tomasz with the Qt repositories) c) be a maintainer's lieutenant in an existing component (we call this position "integrator") >From what I understand, you're offering to help us in both b and c: c now, helping out in an existing project that has a maintainer and, later, with b for new packages you'd like to import in Tizen. If I misunderstood, please let me know. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
