-
Notifications
You must be signed in to change notification settings - Fork 2
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
open source this repo #37
Comments
@andistuder: What makes it a good candidate? I think it's good to articulate the reasons - this helps significantly with expediting the process. Personally, I'd rather wait until after we've used it ourselves successfully and are happy with the way the code. |
I agree with @andistuder but with @sgerrand as well 😸 I think we should give it some time for production testing and polishing. |
@sgerrand IMO, in general good candidates solve something that other people may need to solve also; without giving away trade secrets. For Loga, our tool to standardise and aggregate logs both is the case. To the timing: personally I would prefer to have repos public from the start as visibility can have positive impact on how we write code. Plus, making an existing project public is often a bit of a hurdle that is then never taken. The 0.x version should indicate to users that the project is in pre-production state. |
@whamilton42 @timstott @RafaelPC @sgerrand given we are now in v1.x, maybe now the time has come to open source this gem? |
👍 for opening the gem, but let's finish https://github.com/FundingCircle/loga/milestone/2 because at the moment it is a bit unusable (we all use |
All,
|
We've agreed with @fernandezj to disable the wiki in favour of keeping the README. I think @sgerrand has reviewed the open issues/PRs Tomorrow I will spend time with @mcsche on the security aspect 🎉 |
Should we remove the ticket number from the PR title? |
@0mega: ✨ |
🎉 Introducing Loga, Open sourced since 2016-11-17 |
I think this is a good candidate for a open sourcing.
Needs updating of licence.
The text was updated successfully, but these errors were encountered: