I wrote a couple of AngularJS posts myself, hopefully you think they are worth adding: http://www.grobmeier.de/all-posts-from-this-blog
586 karma · joined July 12, 2011
I wrote a couple of AngularJS posts myself, hopefully you think they are worth adding: http://www.grobmeier.de/all-posts-from-this-blog
http://www.grobmeier.de/hey-i-became-a-vice-president-070720...
Here is another link, which helps you to understand how Apache works: http://www.apache.org/foundation/how-it-works.html
Of course, you don't need to go to the ASF when doing Open Source. I found it great because its all around community there and there are many nice people.
You could also simply start with getting the sources of the tools/lib/framework you use every day, be it on ASF or not. For example, I got the source code of Angular.js because I use it daily. Now when I need to implement something which makes me confused, I am looking into the Angular.js code to understand why it does confuse me. In many cases it's not easy and I leave it up for "later" (aka never), because of the time. But if I am REALLY interested I simply ask on the mailing list how things work. When you have got that knowledge, you can investigate if there is a better way and propose a patch/pull request.
Also simply looking at the issue tracker and finding issue which are matching your skill level are a good start. You could also try to understand issues which are above your skill level, just to understand better how things work.
After all, becoming a contributor is easy: asking and answering questions on mailing lists IS already a contribution to the open source project. Finding out on background, sending patches for typos in the docs, improving unit tests or implementing new features is of course a bigger contribution.
If you are serious about getting into open source, then my advise is to flesh out an hour a day and walk intensive through code you find interesting. If it bores you, take something else. If not, understand things and simply get in touch with the dev, hopefully with some great patches.
In this case, the copy/paste action was just the most boring task I could imagine. Please replace this phrase with "a boring task you cannot escape at best will". It's not really about Excel to phpMyAdmin.
I actually have seen a guy doing something like this before years. Thats why it came to my mind. This guy was not a competent programmer. I should have used a different example maybe. But it is not so easy to find a "boring task" which cannot be automated in todays dev world.
Disclaimer: maybe nothing "deep to say", but this is the story which came to my mind, when I wrote the post. In my opinion, Zen has nothing to do with fatalism as might be understood with this example. Go ahead, make things better. I am thinking about replacing this example, because it came back to me several times now.
In any case, thank you for taking the time reading it and asking this question.
I am not sure if what you said is to be generalized. I am afraid, the image of germany being a deeply philosophical nation of thinkers cannot stand at detailled observation.
But I can say, two things:
First, I try to write short sentences which are straight. My english skills are OK in conversations, but I am far from being a great writer. It takes me a lot of time to write, and almost in every sentence you can hear the german in me. Maybe this creates a specific atmosphere in what I write. But I cannot judge this.
Second, I am studying psychology and thus have to read a lot of philosophical and cultural text. I enjoy it very much and try to learn about cultural aspect as much as possible. I am also a Zen buddhist in real life (not only saying in the post) and learn a lot from my teachers. It all makes me think.
It honors me that you attribute the deep thinking in what I wrote. Again, thank you very much for your comment, it makes me feel good.
Anyway, i fully agree: providing hosting is a hard business. Imaging what 1and1 needs to do for this huge server farm... wow. It's ok for a lot of low traffic sites without much functionality, but in my case I needed more at one point. Now I have the choice between 5.3 and 5.4. Thats neat.
In my region are zero options, as the telekom refuses to give out lines (see article)
Widely available - i was living at various places in germany and the only place which gave me a good connection was Frankfurt. I am now living near munich, its just crap.
The internet isn't going away, nobody said so. But it's in danger to become a two-class internet full of service providers who a) pay to telekom for "managed services" or b) don't pay to telekom. I complain about not respecting "Netzneutralität".
But still he is a community member and PMC of Apache Logging: http://people.apache.org/committers-by-project.html#logging-...
On the other hand, we (the Apache guys) are not liking how the logback project is operating. At least it is me who does not like it, but I guess the others think similar. We want a community driven logging project which uses the Apache License. We surely don't want a logging project which is officially run by a company (like QOS runs logback). I have seen many cases where this does lead into problems.
That said it will be difficult to motivate Ceki to get back to Apache Logging. But we are open to his contributions and hope that there will be a good, technical exchange between both projects.
Another personal note: I am really against person cult. The Apache Logging project has some really great and experienced committers on board. One of them is working on Java logging for around 20 years and he set a very, very high bar for log4j. Having Ceki on-board is definitely of interest, but he is not the only person who knows about logging.
Please have also in mind, that a new log4j2 release is just the beginning of our journey (hopefully).
slf4j and logback are a good combination. Of course there are differences, some are highlighted in the blog post.
From the website - decide yourself. http://logging.apache.org/log4j/2.x/manual/index.html
So why bother with Log4j 2? Here are a few of the reasons.
- Log4j 2 is designed to be usable as an audit logging framework. Both Log4j 1.x and Logback will lose events while reconfiguring. Log4j 2 will not. in Logback exceptions in Appenders are never visible to the application. In Log4j 2 Appenders can be configured to allow the exception to percolate to the application
- Log4j 2 uses a Plugin system that makes it extremely easy to extend the framework by adding new Appenders, Filters, Layouts, Lookups, and Pattern Converters without requiring any changes to Log4j.
- The performance of Log4j 2 is similar to that of Logback. It is slightly slower in some tests and faster in others.
- Due to the Plugin system configuration is simpler. Entries in the configuration do not require a class name to be specified.
- Support for Message objects. Messages allow support for interesting and complex constructs to be passed through the logging system and be efficiently manipulated. Users are free to create their own Message types and write custom Layouts, Filters and Lookups to manipulate them.
- Log4j 1.x supports Filters on Appenders. Logback added TurboFilters to allow filtering of events before they are processed by a Logger. Log4j 2 supports Filters that can be configured to process events before they are handled by a Logger, as they are processed by a Logger or on an Appender.
- Many Logback Appenders do not accept a Layout and will only send data in a fixed format. Most Log4j 2 Appenders accept a Layout, allowing the data to be transported in any format desired.
- Layouts in Log4j 1.x and Logback return a String. This resulted in the problems discussed at Logback Encoders. Log4j 2 takes the simpler approach that Layouts always return a byte array. This has the advantage that it means they can be used in virtually any Appender, not just the ones that write to an OutputStream.
- The Syslog Appender supports both TCP and UDP as well as support for the BSD syslog and the RFC 5424 formats.
- Log4j 2 takes advantage of Java 5 concurrency support and performs locking at the lowest level possible. Log4j 1.x has known deadlock issues. Many of these are fixed in Logback but many Logback classes still require synchronization at a fairly high level.
- It is an Apache Software Foundation project following the community and support model used by all ASF projects. If you want to contribute or gain the right to commit changes just follow the path outlined at Contributing
Still logback is a great framework. The log4j2 team learned of it and I think it is also in the other direction.
My (personal) recommendation is you use slf4j and chose a logging framework to your taste. You might choose based on a specific feature, on issue which has not been resolved in the other framework, on the license or how easily you can contribute.
That said, the log4j2 project is pretty active.
logback / log4j2 are 2 implementations of the slf4j facade. log4j2 is a community driven project and it is maintained with Apache License 2.0. It addresses some issues of logback. If you run into this issues in production, you can switch to log4j2, given that you are using slf4j (which is the recommendation).
commons-logging is pretty dead, and nobody makes a deal about it. It has not been updated for around 5 yrs.
You clearly need to understand the difference between slf4j and logback/log4j2. And you should learn more about what the Apache Software Foundation is doing. I consider it better not to trust a single company when it comes to important things. It has often proven in the past.
Logback has been developed by the same guy who wrote log4j 1.x. He left and log4j 1 was not maintained a long time. But before a good while a few others have teamed up to bring the project back to life. With log4j 2 we have looked closely at other frameworks, including logback, and tried to make things better. Actually we have found a few things which we consider better. Still you need to consider log4j 2.0 is a young framework and in beta. That said, we are always glad about feedback. You and your developers are invited to join us on our mailing list and tell us what you think - good or bad. Thanks again for your interest (and bearing with my english)
You wrote you have the impression LibreOffice is "doing better". What does that mean? Have you observed what OpenOffice is doing? What is your metric? If you have not looked into both projects and if you have not tried both products you simply cannot say that. You are a victim of marketing, probably. "Doing better" is too broad to say. Even when you say "i like LO more" you can't say "doing better" in general, because both project are not really merge-able codewise and cannot be compared. You just can give your own impression, like when you say "Windows" is doing better than "OS X".
You also miss one important point before you choose for which organization you are working. The license. Apache licensed code can be used in commercial products. GPL licensed (as with LO) cannot be used without becoming Open Source itself. This is important, because OpenOffice is the one you would take when you are working on a product which needs to include for example spreadsheet features.
That all said, Open Source has different point of views, but for many of us unpaid developers it is not about marketing. It is about fun of coding. Exploring new things. Make big things happen. I even agree when you say: collaborating on code, releasing and getting users is cool to have. But: nobody needs marketing for that. I have worked on many open source projects without a "marketing division".
What you said about GNU: they do not have a no-modification copyright license.
However in this blog post I outlined that wrong marketing is doing harm to a project. Flames against projects is doing that too. Having media with an opinion when they should make up news in a mostly objective way is bad too.
Still i don't get why there is dicussion. A group of people want to do project A, a group of people want to do project B. Nobody is forced to stick with a project. Everybody can switch project like he wants. I don't get why people are so emotional with these two projects. Again: calm down, let people have their fun.
I am an amateur musician by night. I spread my music only with pseudonym and send only e-mail by pseudonym.
Not sure what kind of e-mails you are going to send. But if you want to make business (and this business is not upsetting anybody basically) I would go with real name. If you do want to make art, I would prefer pseudonym. I actually have had problems in my day job in times when i published art with real name.
Anyway, I have already mentioned in my post that I was an idiot to forget about the installation. Sure, and that is what I have learned about: not to forget again.
That said, hacking is non acceptable no matter what mistakes the owner of a website has done. I really have no respect for such people.