I'm talking about the information visible to volunteers outside the core
project staff. Small science projects don't have the resources (or the
inclination) to follow every twist and turn. Unless you support and enable
volunteer contributions too, you lose a potentially valuable resource for
community computing in general.
On Wednesday, 29 March 2017, 12:11, Oliver Bock <oliver.b...@aei.mpg.de>
wrote:
On 29/03/2017 12:44 , Richard Haselgrove wrote:
> I agree that the SHAs would be more precise, but they'd be ugly to
> display on a public-facing page,
Not sure why the public would need to know that at all anyway :-)
> and less easy to do diagnosis
The admin should have no problem with SHA1s.
> human brain can read five digits from a monotonic sequence, and get an
> idea of vintage at a glance, but it can't do that with non-sequential SHAs.
True, but the above notwithstanding, you could always show the latest
tag in your local repo's history (and how many commits you lack) for
instance. Sure, you'd need proper server release for that but that's a
requirement for BOINC's open source ambitions anyway. There are many
ways to improve readability, if that's needed at all.
> But we would need the latest SHA
> included in the server daemon compilation, not just the user web sources.
Most daemons already have that IIRC.
Best,
Oliver
_______________________________________________
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
_______________________________________________
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
