On 03/23/2016 03:56 PM, Holger Levsen wrote:
Here is a rough timeline I've put together based on the work Holger/Lunar
would like to see on the site -- further feedback welcome:
I think the timeline is roughly fine, just one thing:

Please make sure / be aware that you can test all the things locally, on
some system of yours. I'm usually pretty good at merging things and
bringing them online rather immediatly but there will be times when I'm
not so available and this shouldnt result in you getting stuck.

(And you should have a local testbed anyway, to be able to develop+test
your code. As its mostly about the webpages, you also dont need jenkins
for that nor do you need to be running tests. Just experimenting with
the existing reproduicble.db should be fine.)

I assumed I would be testing things locally -- I have a pretty light laptop (asus zebook) but I doubt it'll give me trouble given the size of the db/website. I might have trouble if I branch out to more computational intensive work..?

things I'm missing here:

- an initial working piece to prove that you understand the setup (eg
   one of the 4 things I suggested in private mail yesterday)
- inclusion of the the 3 other things from those list of 4 :)
I looked into your suggestions (see below) and added the ones I don't think I'll get to to the timeline!

>> Week 7 - Migrate from SQLight to Postgres (with new schema design!)
note that you will also need to migrate the data from the old to the new
database design. and this should be scripted. (and tested locally…)
How else does someone migrate data.. other than scripts? ;)

and it misses creating documentation of the new database scheme!

I'm pro-documentation - documentation is implicit :) I did add a note though.

Status update:
The online Outreachy application has been updated. All that is left is the contribution! Notes/questions about your (Holger's) suggestions for contributions (copied from private email):

  (1) convert bin/reproducible_html_dashboard.sh into python (and/or do the
    above changes suggested by Lunar to the dashboard)
  (2) convert bin/reproducible_html_pkg_sets.sh into python

I don't actually think I have enough time to do one of these conversion, due to the business of this next week (I'm going on a long weekend trip tomorrow) and my only basic familiarity with python and bash scripting. Ran into some file location expectations when trying to run reproducible_html_dashboard.sh -- but I'll ask about this when I actually get to working on it!

  (3) enhance bin/reproducible_json.py to create include an arch agnostic
    summary. currently the json will have results for amd64 and armhf, but
  its not clear which is authorative. the result should be: if it fails in
  some suite/arch combination, the result should be failure.

I'm pretty sure that I can do this quickly enough :) I've run the script on reproducible.db and it looks like we only need to do a little extra data munging. But I'm confused about the goal: - Do we want an additional json file to be published, with information about whether the package succeeds across all architectures? Who is going to do anything with that file? - Or do we want to write an "arch agnositic" summary to reproducible.json instead? Should the "architecture" key be blank or non-existant? (I haven't looked into to whatever is using this file)

Also: I've asked to join the alioth reproducible builds project (username: spectranaut-guest), which I believe will give me access to git.debian.org. I should have a public repo to push changes to soon! :)


Reproducible-builds mailing list

Reply via email to