reproducible: document requirements for remote scheduling

1 files changed, 8 insertions, 0 deletions

diff --git a/TODO b/TODO
index 2e3677d5..0fa6d556 100644
--- a/TODO
+++ b/TODO
@@ -222,6 +222,14 @@ grep '(=.*).,.$' rygel_0.24.2-1.debbindiff.html | uniq -c | sort | grep -c '^\s*
 	<h01ger> well, and everybody in debian-keyring from sid can uplood? :)
 	<mapreri> that would be wonderful.
 
+* enable people to schedule packages:
+** script on alioth, using ssh keys only accessable to the reproducible group and another one for DDs+DMs
+** a daily limit of 50 packages (can be stored in /tmp or such), else it should tell to contact us
+*** for non-reproducible members i would like to see a lower limit of packages allowed to schedule. 
+** the script called should not be reproducible_schedule_on_demand.sh but rather reproducible_remoter_scheduler.sh - or we should teach reproducible_schedule_on_demand.sh proper options: --artifacts --notify --remote-user foo 
+*** implied in this: remote schedulings should notify via IRC, who did the scheduling -> the script on alioth should pass $USER
+
+
 === qa.debian.org*
 
 * udd-versionskew: also provide arch-relative version numbers in output too