From c2a51df3d3a84fa810a3ac5f32d3ebcffdc0464a Mon Sep 17 00:00:00 2001 From: lkcl Date: Tue, 19 Dec 2023 17:34:48 +0000 Subject: [PATCH] --- HDL_workflow/rfp_submission_guide.mdwn | 68 +------------------------- 1 file changed, 1 insertion(+), 67 deletions(-) diff --git a/HDL_workflow/rfp_submission_guide.mdwn b/HDL_workflow/rfp_submission_guide.mdwn index a4091d986..2056ef267 100644 --- a/HDL_workflow/rfp_submission_guide.mdwn +++ b/HDL_workflow/rfp_submission_guide.mdwn @@ -147,73 +147,7 @@ ### email 3 - On Tuesday, December 5, 2023, Luke Kenneth Casson Leighton - wrote: - > - > - > On Tuesday, December 5, 2023, Andrey Miroshnikov via Libre-soc-dev < - libre-soc-dev at lists.libre-soc.org> wrote: - >> Hi Luke, - >> - >> Based on our conversation on bug #701, Luke suggested to start a mailing - list thread which we can use as part of documenting RfP submission in - general. This will then be added to: - >> https://libre-soc.org/HDL_workflow/libresoc_bug_process/ - > - > ah. yes. ok - > - > so first thing: the secret URLs are to be respected and treated - > as plaintext passwords. you DO NOT put them on the internet - > or send them to people on publicly logged Libre-SOC resources. - > - > https://bugs.libre-soc.org/show_bug.cgi?id=1126#c48 - > - > second: you click the "submit" button then fill in your - > bank details and name from the dropdown. then you put - > in the amounts, under each milestone. - > - > third: you go to the bugtracker and fill in the TOML field - > with "name={amount: NNNN, submitted=YYYY-MM-DD}" in that - > EXACT format, because it is machine-readable. - > - > ***EXERCISE EXTREME CAUTION HERE BECAUSE YOU ARE EDITING - > FINANCIAL BOOKKEEPING RECORDS*** - > - > if you are uncertain STOP DO NOT PROCEED ASK FOR ADVICE - > IMMEDIATELY. it is best that you WAIT until someone on - > IRC can walk you through the process, or set up a conference - > call with screen-sharing to REVIEW YOUR CHANGES ***BEFORE*** - > YOU HIT THE BUGZILLA SUBMIT BUTTON. - > - > fourth: you run the budget-sync program LOCALLY on your - > personal machine, and if it produces errors and you know - > how to correct them then do so, but if not STOP, do NOT - > attempt further changes, instead IMMEDIATELY ask for help - > on both IRC and the mailing list. this is a REQUIRED - > (mandatory) action. do NOT if you make a mistake "just leave it" - > as your actions will have consequences for everyone who then - > also tries to run budget-sync. - > - > fifth: find your own task_db/yourname.mdwn file, - > return to the NLnet RFP and cut/paste the relevant - > autogenerated sections into the "results" form. - > - > you *do not* repeat DO NOT have to write a long-winded - > report: you can write one *if it is useful to the project* but - > should in no way feel "obligated to write one just for NLnet". - > if you do write one it should be placed PUBLICLY onto - > Libre-SOC resources, and the *URL* given in the associated - > bugreport under comment #0 (which you can of course edit - > to include it). - > - > basically NLnet are flexible and trusting but MUST have - > ACTUAL EVIDENCE of completion of the milestone, whatever that - > may be, such that an EU Auditor is satisfied that no fraud - > has taken place (yes, this *has* actually been attempted in - > the past, by scammers). - > - > sixth: hit the submit button, review the page and then - > submit the RFP. + > > seventh: the MoU Signatory will have been notified by email, > and should review the submission. DO NOT just "click yes", -- 2.30.2