Re: [boinc_dev] Moving

[Rom Walton]

Howdy Folks,

I'm back on the air, after a detour to Bellevue, Washington.

- Rom

-Original Message-
From: boinc_alpha [mailto:boinc_alpha-boun...@ssl.berkeley.edu] On Behalf Of 
Rom Walton
Sent: Sunday, April 24, 2016 3:10 PM
To: BOINC Developers Mailing List 
Cc: boinc_projects ; 
boinc_...@ssl.berkeley.edu; BOINC Alpha 
Subject: [boinc_alpha] Moving

Howdy Folks,

Starting on Monday, I'm going to be moving to North Carolina.  During the move, 
my web and email server will be down.

My alternate email address during the move is 
walton_...@msn.com.

I believe the only issue that this will cause for the project as a whole is the 
automatic synchronization of the localization files between Transifex and 
Github.

- Rom
___
boinc_alpha mailing list
boinc_al...@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
___
boinc_dev mailing list
boinc_dev@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.

[boinc_dev] Moving

[Rom Walton]

Howdy Folks,

Starting on Monday, I'm going to be moving to North Carolina.  During the move, 
my web and email server will be down.

My alternate email address during the move is 
walton_...@msn.com.

I believe the only issue that this will cause for the project as a whole is the 
automatic synchronization of the localization files between Transifex and 
Github.

- Rom
___
boinc_dev mailing list
boinc_dev@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.

[boinc_dev] Moving from SHA-1 to SHA-256

[Kevin Vinsen]

We understand Google intends to phase out support for certificates using a 
SHA-1 hashing algorithm via degraded visual indicators and warnings in their 
Chrome™ browser. This is expected to start as of version 39 (Nov 2014).

In order to alleviate community concerns we want to update our certificate used 
for the boinc site to use a SHA-256 signed certificate.  The intermediate 
certificate would also be SHA-256 signed.  The root certificate will still be 
SHA-1 signed.

Before we replace our certificates, can someone please confirm that boinc 
clients, for all the various platforms (including Android) are able to work 
with these SHA-256 signed certs?  If this support is only recent, what version 
was this support added (so we can tell people to use at least version )?

Regards
Kevin



___
boinc_dev mailing list
boinc_dev@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.

[boinc_dev] Moving forward

[Charlie Fenton]

I am going to leave this discussion with one last thought, because it is 
starting to feel more like an argument than a friendly, cooperative discussion.

BOINC has been one of the early adopters of GPU computing.  When we began 
working on it, OpenCL was still under development.  Yes, if we were to start 
over from scratch, we would probably do things differently, given the knowledge 
we've gained.  And we probably will do some major overhauls at some point.

But right now, we have limited resources and a large installed base of both 
projects and volunteer crunchers.  So for the time being, we need to build on 
what we already have in place and emphasize being backward compatible wherever 
possible so as not to break the work of our projects and volunteers.

For example, we would like to make the scheduler smarter when dealing with 
multiple GPUs on one computer when some are more powerful than others.  But 
this will require a major logic rework, so it won't happen in the near future.

And for many of the changes some people want, there are other people who want 
the opposite.  For example, some projects feel that having OpenCL separately 
associated with each vendor is important because some hardware architectures 
are not as well suited to OpenCl as others.

Cheers,
--Charlie

___
boinc_dev mailing list
boinc_dev@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.

Re: [boinc_dev] Moving forward

[Raistmer the Sorcerer]

And for many of the changes some people want, there are other people who want 
the opposite.  For example, some projects feel that having OpenCL separately 
associated with each vendor is important because some hardware architectures 
are not as well suited to OpenCl as others.
Sure, it's convenient feature.
Hence it would be good to have some way (and from your prev replies I infered 
it presents already) to have separate OpenCL_* types for different device types 
_and_ generic OpenCL device type that will include all capable devices (maybe 
even with additional separation OpenCL_GPU and OpenCL_CPU as it done in OpenCL 
itself).
 
___
boinc_dev mailing list
boinc_dev@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.

Re: [boinc_dev] Moving BOINC source and development to GitHub?

[Oliver Bock]

On 9/22/12 23:40 , Nicolás Alvarez wrote:
 2012/9/22, Bartosz Kaszubowski bartoszkaszubow...@gmail.com:
 Hello BOINC Devs,

 Did you ever discuss or dispute about moving BOINC development to GitHub? I
 am sure that I do not have to write about all advantages of this platform
 and community gathered around it so I have just move on to the question.

 I'm very curious  - because I did not have enough knowledge about any
 limitations according to university status of BOINC project - is it the
 major reason why to this day BOINC source is not avaiable at GitHub?
 
 To make the source available on github, first the SVN repository
 would have to be converted to Git, which is a hard task (already in
 progress).

Right, and one has to differentiate between git as the underlying SCM
system and GitHub as a hosting platform for git repos. The former being
much more important (and almost there) than the latter...

Oliver

___
boinc_dev mailing list
boinc_dev@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.

Re: [boinc_dev] Moving BOINC source and development to GitHub?

[Jeremy Cowles]

On Sat, Sep 22, 2012 at 2:40 PM, Nicolás Alvarez
nicolas.alva...@gmail.comwrote:

 But I see absolutely no reason to move the *official* development of
 BOINC to github instead of keeping everything in the local
 infrastructure of the university.


I disagree. The amazingly collaborative infrastructure that github provides
is a compelling reason to use it. We recently launched a project on GitHub
and got meaningful contributions almost immediately.

Github's open source ecosystem and their mechanism of highly visible
pull-requests with commentary both work extremely well.

I know moving is a big deal and I'm on the fence about whether it should
really be done or not, but collaboration is definitely a valid argument for
doing it.



 What advantages would that have?
 Github's bug tracker has significantly less features than Trac. I'd
 dare say the same applies to the wiki. And who would migrate our 1210
 bugs and 414 wiki pages? (are you volunteering? ;)



Why would the wiki and bug tracker need to move?  (I'm not making an
argument here, just questioning if we are conflating two ideas that can
actually remain separate)

--
Jeremy
___
boinc_dev mailing list
boinc_dev@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.

Re: [boinc_dev] Moving BOINC source and development to GitHub?

[Carl Christensen]

I disagree. The amazingly collaborative infrastructure that github provides

is a compelling reason to use it. We recently launched a project on GitHub


if potential development volunteers haven't heard of boinc (or seti etc) by 
now, I really doubt going on github will help as they are probably living in 
a cave! ;-)

I'm sorry, but as far as BOINC is concerned it seems like another 
pain-in-the-ass venture with little to no benefit.
___
boinc_dev mailing list
boinc_dev@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.

Re: [boinc_dev] Moving BOINC source and development to GitHub?

[Jeremy Cowles]

On Mon, Sep 24, 2012 at 9:24 AM, Carl Christensen carl...@yahoo.com wrote:

 I disagree. The amazingly collaborative infrastructure that github
 provides
 is a compelling reason to use it. We recently launched a project on GitHub

 if potential development volunteers haven't heard of boinc (or seti etc)
 by now, I really doubt going on github will help as they are probably
 living in a cave! ;-)

 I'm sorry, but as far as BOINC is concerned it seems like another
 pain-in-the-ass venture with little to no benefit.



I think you missed my point -- it's not about new people discovering BOINC,
it's about having good tools for collaboration.

But you're right, there's no guarantee it would yield any measurable return
on the time invested.

--
Jeremy
___
boinc_dev mailing list
boinc_dev@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.

Re: [boinc_dev] Moving BOINC source and development to GitHub?

[Nicolás Alvarez]

2012/9/24 Jeremy Cowles jeremy.cow...@gmail.com:

 On Sat, Sep 22, 2012 at 2:40 PM, Nicolás Alvarez nicolas.alva...@gmail.com
 wrote:

 But I see absolutely no reason to move the *official* development of
 BOINC to github instead of keeping everything in the local
 infrastructure of the university.


 I disagree. The amazingly collaborative infrastructure that github provides
 is a compelling reason to use it. We recently launched a project on GitHub
 and got meaningful contributions almost immediately.

 Github's open source ecosystem and their mechanism of highly visible
 pull-requests with commentary both work extremely well.

Once BOINC moves to Git, setting up a *mirror* in GitHub is trivial.
Quite a few big projects do that, including the Linux kernel (although
Linus Torvalds will *never* accept a GitHub push request as an
official way to contribute a patch ).

But I see no reason to officially move there. Rom Walton already set
up the Git server infrastructure on boinc.berkeley.edu, including (I
think) authentication with the keys that existing developers already
use for SVN.

 What advantages would that have?
 Github's bug tracker has significantly less features than Trac. I'd
 dare say the same applies to the wiki. And who would migrate our 1210
 bugs and 414 wiki pages? (are you volunteering? ;)

 Why would the wiki and bug tracker need to move?  (I'm not making an
 argument here, just questioning if we are conflating two ideas that can
 actually remain separate)

Because Bartosz said move development to GitHub. Development of an
open source project is much more than just the code and version
control.

Moving the repository to github and not the bug tracker gives us an
instant loss: you can't push a commit with fixes #123 in the commit
message and have it close the corresponding bug on our Trac instance,
without extra setup of post-commit hooks notifying the BOINC server,
etc.

-- 
Nicolás
___
boinc_dev mailing list
boinc_dev@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.

[boinc_dev] Moving BOINC source and development to GitHub?

[Bartosz Kaszubowski]

Hello BOINC Devs,

Did you ever discuss or dispute about moving BOINC development to GitHub? I
am sure that I do not have to write about all advantages of this platform
and community gathered around it so I have just move on to the question.

I'm very curious  - because I did not have enough knowledge about any
limitations according to university status of BOINC project - is it the
major reason why to this day BOINC source is not avaiable at GitHub?

Have a nice day,
Bartosz Kaszubowski
___
boinc_dev mailing list
boinc_dev@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.

Re: [boinc_dev] Moving BOINC source and development to GitHub?

[Nicolás Alvarez]

2012/9/22, Bartosz Kaszubowski bartoszkaszubow...@gmail.com:
 Hello BOINC Devs,

 Did you ever discuss or dispute about moving BOINC development to GitHub? I
 am sure that I do not have to write about all advantages of this platform
 and community gathered around it so I have just move on to the question.

 I'm very curious  - because I did not have enough knowledge about any
 limitations according to university status of BOINC project - is it the
 major reason why to this day BOINC source is not avaiable at GitHub?

To make the source available on github, first the SVN repository
would have to be converted to Git, which is a hard task (already in
progress).

But I see absolutely no reason to move the *official* development of
BOINC to github instead of keeping everything in the local
infrastructure of the university. What advantages would that have?
Github's bug tracker has significantly less features than Trac. I'd
dare say the same applies to the wiki. And who would migrate our 1210
bugs and 414 wiki pages? (are you volunteering? ;)

So yes, you do have to write about all the advantages of the platform
if you want to argue for moving to it...

-- 
Nicolás
___
boinc_dev mailing list
boinc_dev@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.