| Summary: | Max needs commit rights to svn | ||
|---|---|---|---|
| Product: | Infrastructure | Reporter: | Max <bogusman222> |
| Component: | Account request | Assignee: | Sysadmin Team <sysadmin-bugs> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | rverschelde, sysadmin-bugs, watersnowrock |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Max
2012-04-05 23:27:21 CEST
Do you have a list of software where you need to update artwork ? Or where you need commit permission ? I think we need to see with maintainer of those software how they want artwork to be updated. Either sent by email, committed directly, or an other way. Did you already discuss this with them ? CC:
(none) =>
boklm Not really. To be honest, I"m not entirely sure where each artwork eventually needs to be, I'm not that familiar (read: not familiar at all) with the build system. But I think that each project that we are working on now belongs to a different package and has a different maintainer. It would waste a lot of time and cause more room for confusion if we cannot commit directly but need to work through a "third party". (In reply to comment #2) > Not really. > > To be honest, I"m not entirely sure where each artwork eventually needs to be, > I'm not that familiar (read: not familiar at all) with the build system. > > But I think that each project that we are working on now belongs to a different > package and has a different maintainer. It would waste a lot of time and cause > more room for confusion if we cannot commit directly but need to work through a > "third party". It would be a lot of help if there was somebody who is very familiar with the build system and maybe could mentor us as a team. Just sort of show us where things go, what needs to be done and such. I think this should be discussed with developers of those software first. To know how to proceed, whether they want this committed directly in the software svn, sent by email for review before, or committed in a specific svn repository for artwork. Well nearly all artwork is the /theme on the svn, there is kde stuff in mageia-kde-config. I am listed as the maintainer for mageia-theme and mageia-gfxboot-theme, however, that is specific to artwork things, and I require help on the technical side of it. So as max says having a mentor for the whole team would be useful, as would have a group or team to maintain packages that have such a wide range of requirements. CC:
(none) =>
watersnowrock Ping on this. I'm heading the Hebrew translation team, so I really do need commit rights to SVN now. Hello, So you need access to the mga-i18n-committers group ? CC:
(none) =>
remi Uh, no actually. I'd forgotten about this bug, closing it as no longer relevant. Status:
NEW =>
RESOLVED
Nicolas Vigier
2014-05-08 18:04:27 CEST
CC:
boklm =>
(none) |