make Github repo the master?

[David Anderson]

I propose making the BOINC repo on Github the "master" repo
(rather than the one on the UCB server).

This will make it easier to control who has commit access,
and will make this info publicly visible.

Any objections or comments?
If not we'll do this in a couple of days.

-- David

[Eric J Korpela]

Will commits still go to the boinc_cvs mailing list?  I depend on that feature. 

-- David

--
You received this message because you are subscribed to the Google Groups "boinc_admin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to boinc_admin...@googlegroups.com.
To post to this group, send email to boinc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/boinc_admin/55ADD1DD.7020809%40ssl.berkeley.edu.
For more options, visit https://groups.google.com/d/optout.

[Christian Beer]

Yes, we can add the boinc_cvs address to github. The format will change as github only sends the commit message and not the actual changes. Those are provided via a weblink to github. If you are a commiter with access to the github repo you can also configure to get such notifications on your personal email.

MfG / Regards
Christian Beer

To view this discussion on the web visit https://groups.google.com/d/msgid/boinc_admin/CAKFuvzaUy5u9xmTS6YKEqhOU73%2BRuHoUB452a4av7O0D3Z%3D6dg%40mail.gmail.com.

[peters...@gmail.com]

Thank you David for trying to make somethings more publicly visible.

May I ask is there anything on the planning stage regarding Public Support.?  The reason I am asking this is that current documentation indicates that the community may ask questions at the official website, Note that the forum is not mentioned.  How is this done on a website?  In Australia it is a law that Public and Private Companies  provide a means whereby the community may ask questions and should the answer be unsatisfactory the software company needs to refer the matter to an appointed Dispute Resolution Officer before it can be referred to an Ombudsman.  Heavy fines are involved if this is not adhered to.  I realize that you are not a Company of any description and neither are you under Australian Law. However, do you think in view of legal Technicalities such issues be considered?  All good software manufacturers including Open Software ones provide a system where a user can send an email to  support and request an answer.  The company normally acknowledge the request for help in an automated reply by providing a reference number the progress of which you may follow and told that he will receive a reply in an anticipated time according to the number of requests and difficulties of the question. Is this not a good idea? After all all of the Open Software companies are run by Volunteers and are not for profit.  So far I find it difficult find where I may address my question since the question has already been asked by a Committer yet it was replied by a question and has not progressed.

Peter Shane (Cruncher Pete).  Keep on crunching and have a nice day...

  Note that at this stage I am not concerned weather I will receive a reply to my question but am concerned of the process that will follow in the future since the PMC stated that they will not reply to questions that is documented.  If a Committer asks for help and is not answered who can he turn to for answers..Is this not part of the responsibility of the Governance system?

[Eric J Korpela]

Be sure to give a shout out when this happens.

On Mon, Jul 20, 2015 at 10:00 PM, David Anderson <da...@ssl.berkeley.edu> wrote:

-- David

[Rom Walton]

I plan on doing the changeover on the 27^th.

 

After the change, everybody should only need to change the git origin repo configuration to https://github.com/BOINC/boinc.git within their local repo.

 

----- Rom

To view this discussion on the web visit https://groups.google.com/d/msgid/boinc_admin/CAKFuvzbSNhTMGc5y7Ft-G-5T2MXrw_A4g-ZS3%3DUAPoGZkA9HLA%40mail.gmail.com.

[Rom Walton]

As of now, the authoritative BOINC repo is on github.

 

Please change your origin repo to point to github.

 

Thanks.

 

----- Rom

 

From: Rom Walton
Sent: Thursday, July 23, 2015 11:30 AM
To: 'Eric J Korpela' <kor...@ssl.berkeley.edu>; David Anderson <da...@ssl.berkeley.edu>
Cc: boinc...@googlegroups.com; BOINC Dev Mailing List <boin...@ssl.berkeley.edu>
Subject: RE: [boinc_admin] make Github repo the master?

 

I plan on doing the changeover on the 27^th.

 

After the change, everybody should only need to change the git origin repo configuration to https://github.com/BOINC/boinc.git within their local repo.

 

----- Rom

 

From: boinc...@googlegroups.com [mailto:boinc...@googlegroups.com] On Behalf Of Eric J Korpela
Sent: Wednesday, July 22, 2015 8:51 PM
To: David Anderson <da...@ssl.berkeley.edu>
Cc: boinc...@googlegroups.com
Subject: Re: [boinc_admin] make Github repo the master?

 

Be sure to give a shout out when this happens.

To view this discussion on the web visit https://groups.google.com/d/msgid/boinc_admin/CAKFuvzbSNhTMGc5y7Ft-G-5T2MXrw_A4g-ZS3%3DUAPoGZkA9HLA%40mail.gmail.com.

[David Anderson]

How do we do that?
-- David

[Rom Walton]

If your using the command line:

https://git-scm.com/book/en/v2/Git-Basics-Working-with-Remotes

 

In TotoriseGit, it is under the settings when you right-click the repo.

 

----- Rom

[Jord van der Elst]

I did it like this for the GUI:
Right click on my local repository, Git-Pull
In the window that opens, click "Manage remotes".
Either add BOINC as a remote, or change the URL from what it was to
https://github.com/BOINC/boinc.git
Click Apply.
Next in the Git Pull window, choose BOINC, check that the branch is
still correct, then click OK.


-- Jord van der Elst.

On Mon, Jul 27, 2015 at 7:17 PM, David Anderson <da...@ssl.berkeley.edu> wrote:
> How do we do that?
> -- David
>
> On 27-Jul-2015 10:15 AM, Rom Walton wrote:
>>
>>
>> As of now, the authoritative BOINC repo is on github.
>>
>> Please change your origin repo to point to github.
>>
>> Thanks.
>>
>> ----- Rom
>>

>> *From:*Rom Walton
>> *Sent:* Thursday, July 23, 2015 11:30 AM
>> *To:* 'Eric J Korpela' <kor...@ssl.berkeley.edu>; David Anderson
>> <da...@ssl.berkeley.edu>
>> *Cc:* boinc...@googlegroups.com; BOINC Dev Mailing List
>> <boin...@ssl.berkeley.edu>
>> *Subject:* RE: [boinc_admin] make Github repo the master?
>>
>> I plan on doing the changeover on the 27^th .

>>
>> After the change, everybody should only need to change the git origin repo
>> configuration to https://github.com/BOINC/boinc.git within their local repo.
>>
>> ----- Rom
>>

>> *From:*boinc...@googlegroups.com <mailto:boinc...@googlegroups.com>
>> [mailto:boinc...@googlegroups.com] *On Behalf Of *Eric J Korpela
>> *Sent:* Wednesday, July 22, 2015 8:51 PM
>> *To:* David Anderson <da...@ssl.berkeley.edu
>> <mailto:da...@ssl.berkeley.edu>>
>> *Cc:* boinc...@googlegroups.com <mailto:boinc...@googlegroups.com>
>> *Subject:* Re: [boinc_admin] make Github repo the master?

>>
>> Be sure to give a shout out when this happens.
>>
>> On Mon, Jul 20, 2015 at 10:00 PM, David Anderson <da...@ssl.berkeley.edu
>> <mailto:da...@ssl.berkeley.edu>> wrote:
>>
>> I propose making the BOINC repo on Github the "master" repo
>> (rather than the one on the UCB server).
>>
>> This will make it easier to control who has commit access,
>> and will make this info publicly visible.
>>
>> Any objections or comments?
>> If not we'll do this in a couple of days.
>>
>> -- David
>>
>> -- You received this message because you are subscribed to the
>> Google Groups
>> "boinc_admin" group.
>> To unsubscribe from this group and stop receiving emails from it, send
>> an
>> email to boinc_admin...@googlegroups.com

>> <mailto:boinc_admin%2Bunsu...@googlegroups.com>.

>> To post to this group, send email to boinc...@googlegroups.com

>> <mailto:boinc...@googlegroups.com>.

>> To view this discussion on the web visit
>>
>> https://groups.google.com/d/msgid/boinc_admin/55ADD1DD.7020809%40ssl.berkeley.edu.
>> For more options, visit https://groups.google.com/d/optout

>> <https://groups.google.com/d/optout>.

>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "boinc_admin" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to boinc_admin...@googlegroups.com

>> <mailto:boinc_admin...@googlegroups.com>.

>> To post to this group, send email to boinc...@googlegroups.com

>> <mailto:boinc...@googlegroups.com>.

>> To view this discussion on the web visit

>> https://groups.google.com/d/msgid/boinc_admin/CAKFuvzbSNhTMGc5y7Ft-G-5T2MXrw_A4g-ZS3%3DUAPoGZkA9HLA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/boinc_admin/CAKFuvzbSNhTMGc5y7Ft-G-5T2MXrw_A4g-ZS3%3DUAPoGZkA9HLA%40mail.gmail.com?utm_medium=email&utm_source=footer>.

>> For more options, visit https://groups.google.com/d/optout.
>>
>

> _______________________________________________
> boinc_dev mailing list
> boin...@ssl.berkeley.edu
> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
>
> To unsubscribe, visit the above URL and
> (near bottom of page) enter your email address.

[David Anderson]

Thanks; that worked for me.
-- David

[Rom Walton]

The git (cli) commands to redirect origin to the github site are:
git remote rm origin
git remote add origin https://github.com/BOINC/boinc

----- Rom

From: boinc...@googlegroups.com<mailto:boinc...@googlegroups.com> [mailto:boinc...@googlegroups.com] On Behalf Of Eric J Korpela
Sent: Wednesday, July 22, 2015 8:51 PM
To: David Anderson <da...@ssl.berkeley.edu<mailto:da...@ssl.berkeley.edu>>
Cc: boinc...@googlegroups.com<mailto:boinc...@googlegroups.com>
Subject: Re: [boinc_admin] make Github repo the master?

Be sure to give a shout out when this happens.

On Mon, Jul 20, 2015 at 10:00 PM, David Anderson <da...@ssl.berkeley.edu<mailto:da...@ssl.berkeley.edu>> wrote:
I propose making the BOINC repo on Github the "master" repo (rather than the one on the UCB server).

This will make it easier to control who has commit access, and will make this info publicly visible.

Any objections or comments?
If not we'll do this in a couple of days.

-- David

--
You received this message because you are subscribed to the Google Groups "boinc_admin" group.

To unsubscribe from this group and stop receiving emails from it, send an email to boinc_admin...@googlegroups.com<mailto:boinc_admin%2Bunsu...@googlegroups.com>.
To post to this group, send email to boinc...@googlegroups.com<mailto:boinc...@googlegroups.com>.

To view this discussion on the web visit https://groups.google.com/d/msgid/boinc_admin/55ADD1DD.7020809%40ssl.berkeley.edu.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "boinc_admin" group.

To unsubscribe from this group and stop receiving emails from it, send an email to boinc_admin...@googlegroups.com<mailto:boinc_admin...@googlegroups.com>.
To post to this group, send email to boinc...@googlegroups.com<mailto:boinc...@googlegroups.com>.
To view this discussion on the web visit https://groups.google.com/d/msgid/boinc_admin/CAKFuvzbSNhTMGc5y7Ft-G-5T2MXrw_A4g-ZS3%3DUAPoGZkA9HLA%40mail.gmail.com<https://groups.google.com/d/msgid/boinc_admin/CAKFuvzbSNhTMGc5y7Ft-G-5T2MXrw_A4g-ZS3%3DUAPoGZkA9HLA%40mail.gmail.com?utm_medium=email&utm_source=footer>.

For more options, visit https://groups.google.com/d/optout.

[Nicolás Alvarez]

2015-07-27 18:17 GMT-03:00 Rom Walton <ro...@romwnet.org>:
> The git (cli) commands to redirect origin to the github site are:
> git remote rm origin
> git remote add origin https://github.com/BOINC/boinc
>
> ----- Rom

git remote set-url origin https://github.com/BOINC/boinc

--
Nicolás

[Rom Walton]

Even better.

----- Rom

-----Original Message-----
From: Nicolás Alvarez [mailto:nicolas...@gmail.com]
Sent: Monday, July 27, 2015 5:21 PM
To: Rom Walton <ro...@romwnet.org>
Cc: boinc...@googlegroups.com; BOINC Dev Mailing List <boin...@ssl.berkeley.edu>
Subject: Re: [boinc_dev] [boinc_admin] make Github repo the master?

[Richard Haselgrove]

Does anyone know whether it's possible to display the Github web interface in "most recent change first" order? (so far, I've failed). For active developers, you know which area of code you'll be working in. But for users and amateur bughunters, the question is "what areas of code have changed recently - have they fixed the problem I've reported, or where might the next glitch show up and need testing?"

Even better.

----- Rom

[Rom Walton]

Is this what you are looking for?

 

https://github.com/BOINC/boinc/commits/master

 

----- Rom

--

You received this message because you are subscribed to the Google Groups "boinc_admin" group.

To unsubscribe from this group and stop receiving emails from it, send an email to boinc_admin...@googlegroups.com.
To post to this group, send email to boinc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/boinc_admin/283284114.3739869.1438038127572.JavaMail.yahoo%40mail.yahoo.com.

[yava...@gmail.com]

Github is a popular resource so personally I don't have any objections.

However, branching off of that, today's BOINC web server crash illustrates the need for a mirror (multiple preferably) for the clients. As of this moment, sofar as I know, every project points to the BOINC server for the clients... Come to think of it, why can't we have the individual projects mirror at least the suggested clients?

Also, as an alternate, maintaining a separate FTP server.

[Peter shane]

I am willing to offer my personal website which is in limbo at the moment for whatever the need of BOINC is.  I can give my credentials to one of the Devs to set up the site as needed.

Peter Shane (Cruncher Pete)
BOINC Critique

--
You received this message because you are subscribed to a topic in the Google Groups "boinc_admin" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/boinc_admin/mk9Z6UxjkZ0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to boinc_admin...@googlegroups.com.

To post to this group, send email to boinc...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/boinc_admin/1f058cab-32a4-436f-bc79-7b4f559a2a66%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

---

This email has been checked for viruses by Avast antivirus software. www.avast.com

[Oliver Bock]

On 02/08/15 01:38, yava...@gmail.com wrote:
> However, branching off of that, today's BOINC web server crash
> illustrates the need for a mirror (multiple preferably) for the clients.
> As of this moment, sofar as I know, every project points to the BOINC
> server for the clients... Come to think of it, why can't we have the
> individual projects mirror at least the suggested clients?

I like the idea and will discuss it internally for E@H. As long as the
"latest" upstream client for each OS variant is available at a constant
URL each project can choose to mirror it locally if it wants to do so...

JM2C,
Oliver

[richard.h...@gmail.com]

The BOINC client installers - including older versions - should be relatively easy to crowdsource from the thousands of users who have their own download archive. What would be most useful would be to have an alternate url (or multiple urls) which has the full platform detection and version control features of BOINC's own site. That's not urgent - recent installers are already starting to appear via peer-to-peer sharing, in true distributed computing style.

What is more serious in the long term is the potential loss of the various documentation Wikis - for both project administrators and volunteers. Oliver, as well as your greatly appreciated offer to discuss download mirroring internally within Einstein, could you ask your local representative on the Project Management Committee to instigate a BOINC-wide forward plan to eliminate this 'single point of failure'?

[Oliver Bock]

Hi Richard,

On 03/08/15 11:21, richard.h...@gmail.com wrote:
> Oliver, as well as your greatly appreciated offer to discuss
> download mirroring internally within Einstein, could you ask your local
> representative on the Project Management Committee to instigate a
> BOINC-wide forward plan to eliminate this 'single point of failure'?

He should be aware about it via this list but I forwarded your inquiry
again, just in case.

Oliver

[David Anderson]

The BOINC server's file system failed on Friday night,
and our sysadmins (Matt and Jeff) have managed to get most of the server functions,
including client download, working on another machine,
though there are still some issues with the MySQL database.

This was a wakeup call WRT server reliability.
We didn't have a plan for dealing with failures,
and it turns out we weren't even doing DB backups.

We'll fix this; e.g. by running the BOINC server
on a VM instead of bare hardware, and doing snapshots.
We should be able to get automatic failover.
I'll send details in a day or two.

-- David

[Rom Walton]

Can we break out the server functions into multiple VMs?

It would be nice to separate out the front-end (public website/downloads), Interactive (forums/wikis), and back-end stuff (all-projects list/alpha/test projects).

----- Rom

--
You received this message because you are subscribed to the Google Groups "boinc_admin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to boinc_admin...@googlegroups.com.

To post to this group, send email to boinc...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/boinc_admin/55BFDA16.8080201%40ssl.berkeley.edu.

[David Anderson]

Yes; let's think about that once we're stable again.

[Yavanius Gekkō Misuto]

I think going forward from this point the project should be looking at dividing up the way machines (real and virtual) handle tasks and redundancy. For the larger projects, I think having them mirroring the information and the clients would be beneficial. The smaller and younger projects may still need to rely on this being hosted off their servers due to space and bandwidth restrictions.

Similar to Linux, I believe it would be beneficial once the mirrors are established to automatically rotate through them whenever someone needs access...

I wonder though it would be better if we could establish a type of BB that can also serve as a mailing list too (being able not only to receive but reply back to messages). Right now, there are multiple mailing lists and it's somewhat of a hunt to find them and determine what list does what...

To view this discussion on the web visit https://groups.google.com/d/msgid/boinc_admin/55BFEF3A.6030105%40ssl.berkeley.edu.

[Yavanius Gekkō Misuto]

How about offering torrents? You only need to seed it once (assuming no problems with the process). The only thing that concerns me is how does a user verify they have a legit client? Is there something they can do? Is it something BOINC needs to do to the installer to verify the files are correct?

With a torrent, a project would only need to list it and at that point the project servers no longer are involved. Minimal space and bandwidth involved...