Many of you have seen minutes of the recent OpenNTF Board meeting... Probably, you have noticed the IP Manager issue:
Peter Announced that he has been "laid off" as a contractor at IBM effective immediately. OpenNTF Group scrambling to find funding for Peter Tanner's invaluable work for the OpenNTF Entity. Looking for options for hiring Peter as a consultant. We have a quorum. Peter Tanner excused himself from the conversation. Outstanding $4,250.00 in accounts receivable. Discussion of a contingency plan to get Peter back. Working on approving 30 hours for Peter.
Tweets have started just after a couple of hours and Bruce Elgort, the Chairman has notified an incoming blog entry...
I don't want to bring a discussion about IBM's involvement about this. Because; very little of us know what is going on in the background and I'm pretty sure the board and many IBMers did what they have to do... Besides, I never thought that IBM will pull back OpenNTF's progress and I am personally faced lots of situations that IBM spending incredible amount of money and energy on its community.
On the other hand, I also witnessed so many interesting "we want it but we cannot do it" cases inside IBM. So let's put this issue to the OpenNTF and IBM people and trust them about they could do what needs to be done.
So why I'm blogging about this?
I have seen some good comments and positive approaches about funding OpenNTF. For example, a fund-raising activity is being suggested. It would be a very good contribution to OpenNTF but it's a temporary solution. We need a more solid and permanent solution.
We should first accept that OpenNTF is more than a community right now. With the extension library and development contests; OpenNTF became a center of gravity in Domino development (mainly XPages). Although there are 'side' communities, OpenNTF circle is still making the largest contribution to the development.
Secondly, we have to understand why OpenNTF have been incorporated and why we need to hire an IP manager. This has been undervalued or ignored in the community as far as I see.
As you may have noticed, IBM contributed lots of source code in the last years. They have also assigned a team of developers for extension library, mobility and social enabler projects. Lots of companies are also contributing these projects with different motives. So if you are a 'code provider', it's an important factor to work in a regulated platform which provides legal protection for your code and intellectual property.
Get back to the consumer side; many large companies have restriction policies that regulates the use of open source codes. Suppose you are developing your own application (to use or to sell). You can't just google something and use the first code piece you have seen! That would end up a legal case, tagged with a number of figures. But you are pretty sure about that OpenNTF projects are cleared by an IP authority. That differs a lot...
So I hope you have been convinced till this point, about how important OpenNTF is...
Somehow, OpenNTF should be funded. Expecting this from contributors will not be fair. IBM should certainly arrange some funds (because, obviously they have the most benefit from OpenNTF). In addition, it is the time for member companies to pay something for our membership.
My company has been the member of OpenNTF. This has nothing to do with my personal contribution. I would prefer to be a personal contributor, but didn't. Why?
Because being the member of OpenNTF is an important title for my company. Customer looks at my company resumé, and they see OpenNTF contributions of Developi, not me... OpenNTF are keeping my brand name on their web site, retweeting my XPages activities and leveraging my brand in the community. That's why I owe some membership fee to OpenNTF.
My suggestion is simple. It's not going to cover all expenses of OpenNTF; but I'm sure it will help. OpenNTF would create a formulation for a membership fee according to some criteria (employee count, international presence, financial figures, etc.)
There are additional potential approaches, like building the famous AppStore for XPages solutions, getting more advertisements, etc. All these would be discussed in the future...
We should be open-minded about those alternatives. OpenNTF is more than a community right now. We are all part of it and we are receiving some benefits from OpenNTF.
Two critical HTTP problems in Domino 9...
Fri, Mar 29th 2013 6:48a Serdar Basegmez After I upgraded my servers to Domino 9, I have found two problems affecting HTTP task. 1. Redirect TCP to SSL problem... My HTTP task stopped responding just after the upgrade. When I look into thread logs I saw that it was redirecting every requests to the same URL! After a couple of tests, I found that if you have "Redirect TCP to SSL" checked in your Internet Site document, it fails with infinite redirection problem. I posted the issue into the N/D 9.0 Social Edition forum and [read] Keywords: administration
Happy Pi Day present: Pi Calculator for XPages...
DOTS Deep Dive 4: I can schedule myself...
Thu, Feb 21st 2013 5:20a Serdar Basegmez Finally, we will be able to enable FeedMonster for CollaborationToday project. While doing final touches, I have been challenged by a question: "Can we schedule DOTS tasklets programmatically?" Actually, this is in the wish list for the next version of DOTS. But we can do some trick here. I didn't test this on Domino 9 but it should work. Here is the code: package org.openntf.news.playground.tasklets; import org.eclipse.core.runtime.CoreException; import org.eclipse.core [read] Keywords: domino
DOTS Deep Dive 3: Warning for Deadlocks
Thu, Feb 14th 2013 7:03a Serdar Basegmez Last time, I have blogged about the importance of the importantance of canceling tasklets... In most of the time, canceling a task is a 'choice' you have. You might want to stop the task for a reason. However, a very important problem is falling into deadlocks. If somehow your code falls into a deadlock or stuck situation, that would lock your DOTS container entirely. DOTS uses a basic mechanism for identifying scheduled tasklets that are stuck. Every tasklet starts its life with a pre [read] Keywords: ibm
DOTS Deep Dive 2: Cancel me or I will crash your server...
Wed, Feb 13th 2013 3:53a Serdar Basegmez I just wanted to emphasize an important functionality within DOTS... One of our slides in the recent DOTS session in IBM Connect 2013, we have talked about the "monitor" argument in tasklets. It has two important uses. First of all, you might let DOTS container know about your progress. Second, it allows you to cancel your task in a less-disruptive manner. Let's dive into code here. Our tasklet is running every five seconds and wait 30 seconds each run: @RunEvery( every=5, [read] Keywords: domino
DOTS Deep Dive 1: Art of Scheduling Tasklets
Mon, Feb 11th 2013 4:02a Serdar Basegmez After a successful IBM Connect session, I started a series of posts, based on feedbacks I received from other developers. There was a little thing I didn't test before the session and this issue has been asked a couple of times: Possible conflicts between scheduled tasklets. Unfortunately, current implementation within DOTS is based on single threaded approach for tasklets. There are three different threads responsible in DOTS tasklet container for scheduled, manual and triggerred tasklet [read] Keywords: domino