-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cleaning up ropenscilabs #291
Comments
{travis} and {circle} should go to ropensci imo. Currently {circle} is in review and I just recently found a way for http testing which seems to work (via {vcr}). Right after {circle}, {travis} should follow. Unfortunately my time is limited so this process goes slowly. Happy to accept help :) Related to all the {tic} demo repos: I was never a fan of them and not sure if they are of any help. According to @krlmlr they were asked for when initialising the project. Let's see what @krlmlr opinion is on this. |
If these repos are required by documentation, we can move them elsewhere. If not, let's archive. |
ping @jeroen |
I see |
In theory yes but I would first want to check for remaining doc references and merge #295 first. Then we could archive (maybe I can even do it myself?) - need to check. |
@jeroen Travis funtionality has been removed and all references to the example repos in the README as well. The mentioned repos can be archived. |
Thanks for your help in cleaning up ropensci! I have now archived the above repo's. |
We are trying to clean up the ropenscilabs organization. The idea is that this organization should mostly be a temporary home for experimental projects. Mature projects should be moved either to
/ropensci
or the maintainer github account. Abandoned projects will eventually get moved to ropensci-archive.It seems like
tic
depends on many ropensci labs projects:Are all these projects still active? What would be a good long-term home for these repositories? It almost looks like you need a
tic-org
on github?The text was updated successfully, but these errors were encountered: