I happened to be looking through the admin features of the decapod googlecode space today. Before, we were not able to delete a repository, there was only a facility to disabled old repos. Now, it appears, that you are able to actually delete a repo.
For Decapod we have two old repos that have been disabled: decapod-server and decapod-genpdf. This means that they are inaccessible, but still hanging around. Since we don't use these anymore at all, I'd like to fully remove them. It had been the intention in the first place to drop them, and it seems that it will only add confusion for future developers if we leave them here. Are there any objects to me performing this action?
Additionally, we have some old repos that we will not be using from 0.5 and beyond: stitching and decapod-infusion. These are necessary for Decapod 0.4 though. I think we should keep these for the time being, but am open to discussion.
Justin Obara <obara.jus...@gmail.com> writes:
>For Decapod we have two old repos that have been disabled:
>decapod-server and decapod-genpdf. This means that they are
>inaccessible, but still hanging around. Since we don't use these
>anymore at all, I'd like to fully remove them. It had been the
>intention in the first place to drop them, and it seems that it will
>only add confusion for future developers if we leave them here. Are
>there any objects to me performing this action?
Don't delete -- just remove the files and leave a single README in each
one, containing a forwarding pointer to wherever you want people to go
for the latest stuff.
>Additionally, we have some old repos that we will not be using from
>0.5 and beyond: stitching and decapod-infusion. These are necessary
>for Decapod 0.4 though. I think we should keep these for the time
>being, but am open to discussion.
These repos have probably been inaccessible for over a year or two. Since they were disabled, they aren't viewable at all. Would you suggest that I reopen them and replace the contents with the README pointing to the correct locations.
Also, for the other repos I mentioned, where the code is only valid up to a certain version, is it better to close off the repos with the README or leave them as is?
Thanks
Justin
On 2012-05-18, at 1:38 PM, Karl Fogel wrote:
> Justin Obara <obara.jus...@gmail.com> writes:
>> For Decapod we have two old repos that have been disabled:
>> decapod-server and decapod-genpdf. This means that they are
>> inaccessible, but still hanging around. Since we don't use these
>> anymore at all, I'd like to fully remove them. It had been the
>> intention in the first place to drop them, and it seems that it will
>> only add confusion for future developers if we leave them here. Are
>> there any objects to me performing this action?
> Don't delete -- just remove the files and leave a single README in each
> one, containing a forwarding pointer to wherever you want people to go
> for the latest stuff.
>> Additionally, we have some old repos that we will not be using from
>> 0.5 and beyond: stitching and decapod-infusion. These are necessary
>> for Decapod 0.4 though. I think we should keep these for the time
>> being, but am open to discussion.
>> Thanks
>> Justin
> -- > You received this message because you are subscribed to the Google Groups "Decapod" group.
> To post to this group, send email to decapod@googlegroups.com.
> To unsubscribe from this group, send email to decapod+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/decapod?hl=en.
Justin Obara <obara.jus...@gmail.com> writes:
>Thanks for the feedback.
>These repos have probably been inaccessible for over a year or
>two. Since they were disabled, they aren't viewable at all.
>Would you suggest that I reopen them and replace the contents with the
>README pointing to the correct locations.
Oh -- if they've been down for that long and no one complained, then
nah, it's probably not worth putting forwarding pointers there now.
>Also, for the other repos I mentioned, where the code is only valid up
>to a certain version, is it better to close off the repos with the
>README or leave them as is?
IMHO better to have one last revision that deletes obsolete code
(leaving it in the history, of course) and replacing it with a README
explaining what's going on.
>> Justin Obara <obara.jus...@gmail.com> writes:
>>> For Decapod we have two old repos that have been disabled:
>>> decapod-server and decapod-genpdf. This means that they are
>>> inaccessible, but still hanging around. Since we don't use these
>>> anymore at all, I'd like to fully remove them. It had been the
>>> intention in the first place to drop them, and it seems that it will
>>> only add confusion for future developers if we leave them here. Are
>>> there any objects to me performing this action?
>> Don't delete -- just remove the files and leave a single README in each
>> one, containing a forwarding pointer to wherever you want people to go
>> for the latest stuff.
>>> Additionally, we have some old repos that we will not be using from
>>> 0.5 and beyond: stitching and decapod-infusion. These are necessary
>>> for Decapod 0.4 though. I think we should keep these for the time
>>> being, but am open to discussion.
>>> Thanks
>>> Justin
>> -- >> You received this message because you are subscribed to the Google
>> Groups "Decapod" group.
>> To post to this group, send email to decapod@googlegroups.com.
>> To unsubscribe from this group, send email to
>> decapod+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/decapod?hl=en.
> Justin Obara <obara.jus...@gmail.com> writes:
>> Thanks for the feedback.
>> These repos have probably been inaccessible for over a year or
>> two. Since they were disabled, they aren't viewable at all.
>> Would you suggest that I reopen them and replace the contents with the
>> README pointing to the correct locations.
> Oh -- if they've been down for that long and no one complained, then
> nah, it's probably not worth putting forwarding pointers there now.
>> Also, for the other repos I mentioned, where the code is only valid up
>> to a certain version, is it better to close off the repos with the
>> README or leave them as is?
> IMHO better to have one last revision that deletes obsolete code
> (leaving it in the history, of course) and replacing it with a README
> explaining what's going on.
> Best,
> -K
>> On 2012-05-18, at 1:38 PM, Karl Fogel wrote:
>>> Justin Obara <obara.jus...@gmail.com> writes:
>>>> For Decapod we have two old repos that have been disabled:
>>>> decapod-server and decapod-genpdf. This means that they are
>>>> inaccessible, but still hanging around. Since we don't use these
>>>> anymore at all, I'd like to fully remove them. It had been the
>>>> intention in the first place to drop them, and it seems that it will
>>>> only add confusion for future developers if we leave them here. Are
>>>> there any objects to me performing this action?
>>> Don't delete -- just remove the files and leave a single README in each
>>> one, containing a forwarding pointer to wherever you want people to go
>>> for the latest stuff.
>>>> Additionally, we have some old repos that we will not be using from
>>>> 0.5 and beyond: stitching and decapod-infusion. These are necessary
>>>> for Decapod 0.4 though. I think we should keep these for the time
>>>> being, but am open to discussion.
>>>> Thanks
>>>> Justin
>>> -- >>> You received this message because you are subscribed to the Google
>>> Groups "Decapod" group.
>>> To post to this group, send email to decapod@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> decapod+unsubscribe@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/decapod?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "Decapod" group.
> To post to this group, send email to decapod@googlegroups.com.
> To unsubscribe from this group, send email to decapod+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/decapod?hl=en.
Justin Obara <obara.jus...@gmail.com> writes:
>Thanks for the advice. I plan on following the steps you
>outlined. I've filed a ticket in our issue tracker for it.
>http://issues.fluidproject.org/browse/DECA-266
Cool! Best of luck with the project, as always!...
>> Justin Obara <obara.jus...@gmail.com> writes:
>>> Thanks for the feedback.
>>> These repos have probably been inaccessible for over a year or
>>> two. Since they were disabled, they aren't viewable at all.
>>> Would you suggest that I reopen them and replace the contents with the
>>> README pointing to the correct locations.
>> Oh -- if they've been down for that long and no one complained, then
>> nah, it's probably not worth putting forwarding pointers there now.
>>> Also, for the other repos I mentioned, where the code is only valid up
>>> to a certain version, is it better to close off the repos with the
>>> README or leave them as is?
>> IMHO better to have one last revision that deletes obsolete code
>> (leaving it in the history, of course) and replacing it with a README
>> explaining what's going on.
>> Best,
>> -K
>>> On 2012-05-18, at 1:38 PM, Karl Fogel wrote:
>>>> Justin Obara <obara.jus...@gmail.com> writes:
>>>>> For Decapod we have two old repos that have been disabled:
>>>>> decapod-server and decapod-genpdf. This means that they are
>>>>> inaccessible, but still hanging around. Since we don't use these
>>>>> anymore at all, I'd like to fully remove them. It had been the
>>>>> intention in the first place to drop them, and it seems that it will
>>>>> only add confusion for future developers if we leave them here. Are
>>>>> there any objects to me performing this action?
>>>> Don't delete -- just remove the files and leave a single README in each
>>>> one, containing a forwarding pointer to wherever you want people to go
>>>> for the latest stuff.
>>>>> Additionally, we have some old repos that we will not be using from
>>>>> 0.5 and beyond: stitching and decapod-infusion. These are necessary
>>>>> for Decapod 0.4 though. I think we should keep these for the time
>>>>> being, but am open to discussion.
>>>>> Thanks
>>>>> Justin
>>>> -- >>>> You received this message because you are subscribed to the Google
>>>> Groups "Decapod" group.
>>>> To post to this group, send email to decapod@googlegroups.com.
>>>> To unsubscribe from this group, send email to
>>>> decapod+unsubscribe@googlegroups.com.
>>>> For more options, visit this group at
>>>> http://groups.google.com/group/decapod?hl=en.
>> -- >> You received this message because you are subscribed to the Google
>> Groups "Decapod" group.
>> To post to this group, send email to decapod@googlegroups.com.
>> To unsubscribe from this group, send email to
>> decapod+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/decapod?hl=en.
