|
21)
Message boards :
Projects :
Project Retirement Policy
(Message 59816)
Posted 18 Jan 2015 by Cruncher Pete Post: Eight days ago I have indicated that I have a concern with the way we promulgate or state what project is considered Active, Inactive or Retired. To date my concern has not been answered adequately, indeed my question have not been answered in that time. I have opened this thread with the following in thread 59546 on Jan 11, 2015: Quote: Whilst I am aware that BOINC has a Policy on Project autonomy in which it is stated that there is no Central Directory or approval process, I wonder if we should have an internal BOINC Policy which dictates when a project is considered, Active, Inactive and or Retired. Unquote. Ageless the Admin of this Message Board indicated that there is a policy on this but did not state that it is an official policy. It appeared to be vague and not consistent in the administration of that policy, I and others have questioned its origin and legitimacy. To date I have not received a reply to my question if that policy is promulgated somewhere as an Official Policy or it is an Ad Hoc one that Ageless thinks it should be. As a volunteer who spent thousands of dollars in supporting BOINC Projects, I demand an answer for I consider it my right to know why some projects appear to be favored and included in a list of Projects that we might pursue whilst others are not in the list. Why some projects are declared as Retired, removed from the list in less than a month whilst others are kept in the active list after nine months of inactivity?I am well aware that Stat sited have their own reasons what is considered active and Retired but because of their differences as a volunteers I was hoping that BOINC would lead the field here and provide an example to follow. Jord, again, please answer my question: Where is the policy as stated by you written in other than this forum.? Is it to be considered an official policy and if it is how will project and or users know of its existence.? I am not arguing the point, I am seeking answers for surely there must be a better and fairer way of promulgating what projects are considered Active, Inactive or Retired. Keep on crunching and have a nice day... |
|
22)
Message boards :
Projects :
Project Retirement Policy
(Message 59731)
Posted 17 Jan 2015 by Cruncher Pete Post: Jord, Please clarify your statements for I am not sure if I am reading the meanings of it correctly. I am sorry that you have trouble with my English and I can not speak Dutch. To make it a little simpler, let us take it one at a time. In message 59582 you stated: Quote: "Only projects that have a public production status, who have announced to the world (through e.g. the boinc_projects email list) about who they are and what they plan to do, who have a budget of sorts and who have a good description in English on their web site, are considered active and eligible for the list. Projects with an Alpha, Beta, test or whatever other status, and who don't advertise their presence to the world, plus those who leave everything on their web site in their mother tongue language aren't really considered. No matter how long they've been throwing out work." Unquote. My question was and still is. Where can this policy be found or is this one that you think should apply? The reason for my question is that it is not very clear and I doubt that it is an Official BOINC Policy. Others have asked you to clarify your statement about Alpha, Beta states... In the event that your statements are Official Policy, once again please tell us where we or the Project Admins can read it. In particular how would they know that it is a requirement. Keep on crunching and have a nice day... |
|
23)
Message boards :
Projects :
Project Retirement Policy
(Message 59691)
Posted 16 Jan 2015 by Cruncher Pete Post: My concern is that these lists are not updated, possibly because there is no real policy about what is considered active, inactive, or Retired project. Jord, Please clarify your statements for I am not sure if I am reading the meanings of it correctly. In all good faith, I pointed out the inefficiency of the ways we handle and promulgate which projects is available to a user and when should we declare a project Inactive or Retired. 1. Policy as to what project should be deemed Active. You have appeared to point out a policy regarding this. May I ask is this written as a policy somewhere or it is just your idea what it should be. As it has been pointed out by someone else as well, I can not determine which project is considered in a production status or in Beta etc for most projects do not promulgate that on their website. Are projects required to promulgate their status to the BOINC email list, if so where is it stated that it is a requirement? Please explain why should ABC@Home should still be considered Active. At best the description should be Inactive. I repeat just because the Admin stated three months ago that she HOPE to keep the project running despite the fact that she was told that she is not on the University staff and therefore has no saying on the matter. Remember that there is nothing to that effect on their News site just some obscure statement hidden in their Message Board. It has been Inactive since April last year. How long are we going to waste our time searching every projects Message Board for News. I would like to see a clear unambiguous policy on this. 2. Administrator to maintain an up to date list. You indicate that you are concerned who is going to do this extra work of constantly checking projects. May I suggest that once a clear policy is formulated ask for volunteers. For example I am sure that there are plenty of volunteers like me who are Retired and have the time to police it. All you got to do is ask and select the best candidate for the job. This concludes my input, I do not wish to debate it any further for it could become an argument, I leave it up to the rest of the BOINC Community. |
|
24)
Message boards :
Projects :
Project Retirement Policy
(Message 59546)
Posted 11 Jan 2015 by Cruncher Pete Post: Whilst I am aware that BOINC has a Policy om Project autonomy in which it is stated that there is no Central Directory or approval process, I wonder if we should have an internal BOINC Policy which dictates when a project is considered, Active, Inactive and or Retired. It is getting very time consuming for users to research the status of a project as more and more projects either do not communicate with their users by keeping them up to date with News on their websites or just simply do not issue any Work Units or just simply disappear for months on end without explanation of any sort. For example of the problems I am talking about: 1. BOINC Acive Project list as stated by BOINCStats as at Jan 11, 2015 as well as the official wiki pages list 68 Active projects. Without going into too deep, ABC@Home has not exported stats for 223 days and its webpage is inaccessible. DISTRrtGEN has not issued any WU's since Apr 2014 and there is no News about its future intentions. 2. In BOINC Manager > Tools > Add Projects only lists 41 projects as Active including the two as mentioned above, yet misses current Active projects like Bitcoin Utopia, Citizen Science Grid, SRBase, TN-Grid, WUProp amongst others. My concern is that these lists are not updated, possibly because there is no real policy about what is considered active, inactive, or Retired project. Secondly because it is time consuming to keep these lists up to date no body is apppointed to keep them updated. Since currently 27 so called Active projects are missing from the list, users in particular New ones will give up after being told time and time to please try later. My suggestion is to create an official policy to remove a project from our list of Active Projects after a reasonable time during which a project manager would have time to advice the users in their News Section what is going on. For example: No Work Units issued and no explanation given for a Month the project is removed as Retired. If there is a satisfactory explanation for their absence after that period, it can be replaced as Active again. If there is News that the project will not be issuing work Units say for three months than the project should be placed in the Inactive list. As regards the list as promulgated by BOINC, I would like somebody to oversea it to make sure it is up to date I am sure somebody will have time to maintain it if we have a policy to follow. Keep on crunching and have a nice day. |
|
25)
Message boards :
Projects :
Project suitability for BIONIC?
(Message 35637)
Posted 7 Nov 2010 by Cruncher Pete Post: I like to suggest that BOINC alpha test is not suited to be listed as a BOINC Project. The Message Boards relating to this project and the project has not been active for months or years. There has been no WU's provided to the general public for well over a year. As Volunteers, why are we subjected to waste our time day in day out to check if there is WU's available or not if there is no intention to open the project to the general public or in deed there is no explanation why it was stopped in the first place.. Surely, there is sufficient indoor testers to carry out testing without wasting our time. Time to close it and declare it Retired Project. Mr Anderson, you should know better that this is not a good way of advertising BOINC. The cost of volunteering is not cheap, you should consider the consequences... |
|
26)
Message boards :
Teams :
Aussie Alliance
(Message 35242)
Posted 16 Oct 2010 by Cruncher Pete Post: Nothing fancy, nothing new, just an ordinary team from Australia, Internationally oriented trying our best to work together as a team and help each other. Why not check us out at http://boinc-aussiealliance.net Join us and give us a hand. We would also love to meet you at our forum: http://boinc-aussiealliance.net/forum See you there... To make the URL simpler, we have changed it to http://aussiealliance.us |
Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.