The idea was to have the task descriptions in separate files in a format
which easily can be parsed and compiled for upload to Google in some
logical directory structure: brlcad_t-shirt.md for example
Then, for each task there is an issue where it can be discussed with a link
to the file with the description. Discussions go to the issue and changes
to the description are going to the file.
The task's issues have labels with the state: draft, final, and uploaded.
A new task gets the draft label. If a task (file) is okey the
corresponding issue has to get the final label. Then an automatism could
go over all issues with final label, upload the corresponding file contents
to Google and give the issues the uploaded label. It they are published on
the GCi website too the corresponding issue can be closed.
Then, we are getting the results. These will be stored along with task
description in a directory structure: .../brlcad_t-shirt/HansDieter for
example.
I find it desirable to have task's descriptions and results close to each
other. Again, for each result an issue should be created with a link to
the corresponding directory. Labels could be new, merged, postponed, etc..
To keep track of all these issues a project and cards could be used.
BTW, I wouldn't require the students to send us pull requests because this
would require them to have something we can pull from. I'm totally fine
with patches.
Regards,
Daniel
2017-11-07 13:44 GMT+01:00 Christopher Sean Morrison <brl...@mac.com>:
>
> > Did you had a look at my github attempt? I tried to utilize issues and
> projects too.
>
> Yes, I did. This is right in line with what I had in mind.
>
> I don’t know the exact mechanics we want to use yet, but we do probably
> want to keep the completed work separate from the task descriptions.
> Completed tasks may be in the form of a pull request, for example, instead
> of as an issue. Otherwise, this is in the right direction. Well want to
> either write our own code or use one of the other org’s scripts for syncing
> task data.
>
> The two main needs we have are 1) some way to semi-automate / manage
> uploading of tasks and 2) a place to retain there work knowing that there’s
> not enough time to review and integrate everything during the contest.
>
> Cheers!
> Sean
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> BRL-CAD Developer mailing list
> brlcad-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/brlcad-devel
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
