summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-webteam/attachments/20110124/394bcd40
diff options
context:
space:
mode:
authorNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
committerNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
commit1be510f9529cb082f802408b472a77d074b394c0 (patch)
treeb175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-webteam/attachments/20110124/394bcd40
parentfa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff)
downloadarchives-master.tar
archives-master.tar.gz
archives-master.tar.bz2
archives-master.tar.xz
archives-master.zip
Add zarb MLs html archivesHEADmaster
Diffstat (limited to 'zarb-ml/mageia-webteam/attachments/20110124/394bcd40')
-rw-r--r--zarb-ml/mageia-webteam/attachments/20110124/394bcd40/attachment-0001.html5
-rw-r--r--zarb-ml/mageia-webteam/attachments/20110124/394bcd40/attachment.html5
2 files changed, 10 insertions, 0 deletions
diff --git a/zarb-ml/mageia-webteam/attachments/20110124/394bcd40/attachment-0001.html b/zarb-ml/mageia-webteam/attachments/20110124/394bcd40/attachment-0001.html
new file mode 100644
index 000000000..2aafd6e2a
--- /dev/null
+++ b/zarb-ml/mageia-webteam/attachments/20110124/394bcd40/attachment-0001.html
@@ -0,0 +1,5 @@
+A few questions about the maintainers db application, that are more detailed than the initial spec.<br><br><ul><li>Do we need first name, surname for maintainers or we would only be using email?</li><li>If we do store first name, surname are they compulsory, or can be omitted?</li>
+<li>Where do we take the information from? Is there a database at the moment, that we can take maintainers, packages information?</li><li>If information is taken initially from another database, where is the new information created? Or in other words, do we create new media, maintainer, package in the app or is that created somewhere else?</li>
+<li>How do we integrate with ldap? Would that be used to lookup for administration permissions for maintainers? Or would we need different users as admins that are not necessarily maintainers.</li><li>Would the first maintainer be the admin for a particular package?</li>
+<li>Can the admin of a package be changed later on? </li></ul>P.S. The link for the staging/test application is here for anyone that missed it first time (I&#39;m adding it to the wiki as well):<br><a href="http://maintdb.mageia.org.uk/">http://maintdb.mageia.org.uk/</a><br>
+<br><br>
diff --git a/zarb-ml/mageia-webteam/attachments/20110124/394bcd40/attachment.html b/zarb-ml/mageia-webteam/attachments/20110124/394bcd40/attachment.html
new file mode 100644
index 000000000..2aafd6e2a
--- /dev/null
+++ b/zarb-ml/mageia-webteam/attachments/20110124/394bcd40/attachment.html
@@ -0,0 +1,5 @@
+A few questions about the maintainers db application, that are more detailed than the initial spec.<br><br><ul><li>Do we need first name, surname for maintainers or we would only be using email?</li><li>If we do store first name, surname are they compulsory, or can be omitted?</li>
+<li>Where do we take the information from? Is there a database at the moment, that we can take maintainers, packages information?</li><li>If information is taken initially from another database, where is the new information created? Or in other words, do we create new media, maintainer, package in the app or is that created somewhere else?</li>
+<li>How do we integrate with ldap? Would that be used to lookup for administration permissions for maintainers? Or would we need different users as admins that are not necessarily maintainers.</li><li>Would the first maintainer be the admin for a particular package?</li>
+<li>Can the admin of a package be changed later on? </li></ul>P.S. The link for the staging/test application is here for anyone that missed it first time (I&#39;m adding it to the wiki as well):<br><a href="http://maintdb.mageia.org.uk/">http://maintdb.mageia.org.uk/</a><br>
+<br><br>