-
Notifications
You must be signed in to change notification settings - Fork 408
PROPOSAL: ROCKMONGO TO NEW GITHUB ORGANIZATION #133
Comments
why not just fork? fork it and put the new organization link in here. |
It's good etiquettes to get the permission of the original author. He might be willing to add contributors. We should wait for him to respond and if there is no response(say for 2-4 weeks), then only create a fork. |
exactly |
https://github.com/iwind/rockmongo/blob/master/LICENSE.txt#L10 It would appear that the license does not allow you to create an organization with the same name |
One more thing to consider: MongoDB, Inc. is talking to companies/projects whose tools use the words Mongo or MongoDB in their names, about changing what they are called. That's the reason for the recent renames of "MongoChef to Studio 3T" and "RoboMongo to Robo 3T". |
When forking, maybe also renaming it also? Here is a list of Humongous Rocks ;) |
So, what's the situation, has anyone forked so far ? :) I would be glad to help bugfixing, especially the #29 that could be so harmful ! |
i hereby declare this project dead |
We use Robo3T for month and are very happy with this |
hi @beesofts this is a very different thing rockmongo for some use cases is better with its web interface |
@stefanocudini I agree with you but I havent found any living project similar to rockmongo |
as i already said last year, Fork it, give it a new name and then announce the new Name/URL in this issue |
@woodworker I was thinking of doing it! do you think could there be a sufficient number of contributors for a new project? |
?!The question we are all about is.. the project is alive or dead!?
However this situation is very unpleasant :-( I'm a happy fan of this good software!
We ask to the author @iwind if it is willing to make a fork or move it into a new github organization and continue the development with the help of everyone!
我们所关心的问题是项目还活着还是死了?
但这种情况非常不愉快:-(我是这个好软件的快乐粉丝!
我们要求作者 @iwind 是否愿意做一个叉子或将其移动到一个新的github组织,并在大家的帮助下继续开发!
I appeal to all contributors over all those more active:
@sinacloud @rusoft @lawy @wanchaik @sergey-dryabzhinsky @Coderhypo @anapsix
The text was updated successfully, but these errors were encountered: