KDE Commit Policy

[Thiago Macieira]

Cornelius Schumacher wrote:
>On Sunday 25 September 2005 21:03, Thiago Macieira wrote:
>> The current policy is enforced by ACL rules, so there's no need to
>> write them as guidelines. Namely, each application has a subdir in
>> branches & tags, and only the sysadmins and release dudes have write
>> access to branches/KDE and tags/KDE.
>
>That's for the official releases, but what about all the tags and
>branches which are not in KDE and not in work?

Each application has its own subdir, which is created by a sysadmin. 
Inside it, you can create anything. Generally, we expect to find there 
release branches and tags, but some applications create work branches 
too.

>> Moreover, there's branches/work which is free for anyone to use,
>> provided you erase it after you're done using.
>
>Do we have a recommended naming scheme?

All I recommend is that it is descriptive enough to know what 
application/module/library it's about and what its purpose is.

I think examples are in order:
$ svn ls svn://anonsvn.kde.org/home/kde/branches/work
allens_pim/  <== good name: must be kdepim, someone's private branch
coolos_kdm/  <== good name: everyone knows coolo and everyone knows kdm
dbus-kde4/  <== good name: it's either KDE4 ported to DBUS or a KDE4
			 library offering DBUS
kbabel-soc/ <== good name: Summer of Code project on kbabel
kbabel_svn/  <== bad name: isn't kbabel already in Subversion? 
			Maybe it's kbabel with Subversion support, though.
kcall-tng/  <== good name: someone's working on kcall, improving it
kde4/  <== well-known branch
kdebluetooth-libqobex_rewrite/ <== good name: self-explanatory
kdegames-scons/  <== good name, but only because we know about scons
kdehw/ <== bad name; what module was this branched from? 
			What is the purpose?
kdelibs4_snapshot/ <== good name and also well-known-branch
kdemm/ <== I can guess, but I wouldn't list as a good name
kdevelop-pg/  <== kdevelop, but what's the purpose?
kdevelop-scons/  <== kdevelop for scons? kdevelop using scons?
kdevelop3/  <== bad name: shouldn't it be branches/KDE/3.*/kdevelop ?
kdevquanta/  <== KDevelop + Quanta, ok
kdnssd/  <== bad name: what's the purpose of the branch? rewrite?
kdom/  <== bad name: what's the purpose?
keduca/ <== bad name: ditto
khtml-paged/ <== good name: khtml for paged media
knewstuff-features/ <== good name: new features for knewstuff
kode-x/  <== I have no idea what this is
kompare/  <== bad name: why does kompare need a branch?
konversation4/  <== good name (see below)
kopete/  <== bad name: what's the purpose?
kopete-irc_rewrite/  <== good name
kopete4-GJ/  <== good name: someone's (GJ) kopete
kopi-merge/  <== merge branches?
kst/  <== bad name: what's the purpose?
kwordquiz/ <== ditto
make_kget_cool/  <== acceptable, but I'd rather not see them
newtodoview/  <== must be kdepim...
non-x11-kde4/  <== good name
opensync-integration/  <== ok (but no notice of where it's branched from)
posix-acl-support/  <== ok (but no notice of where it's branched from)
sk4/  <== good name (see below)
soc-gtd/  <== summer of code
soc-kdepim-scripting/  <== summer of code
soc-kdevelop4-parser/  <== summer of code
soc-khotkeys-speechrecognition/  <== summer of code
soc-livingkde/  <== summer of code
soc-vizhistory/  <== summer of code
transcript/  <== bad name: what is this?

I listed kdevelop3 as a bad name, while konversation4 and sk4 as good 
names because kdevelop has already had a version 3 released. It should, 
therefore, be in the official branch, not the work ones. The other two I 
assume are work-in-progress or rewrites, even though superkaramba for 
KDE4 could be developed in trunk.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

5. Swa he géanhwearf tó timbran, and hwonne he cóm, lá! Unix cwæð "Hello, 
World". Ǽfre ǽghwilc wæs glæd and seo woruld wæs fréo.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20050925/79a85f2a/attachment.sig>