Public projects phasing out... new solution?

mdittbenner (at nylc)'s Avatar

mdittbenner (at nylc)

13 Apr, 2009 08:21 PM

I am investigating signing up for my organization and was looking for some documentation on public projects when I began seeing that public projects will be phased out. In addition to using Lighthouse for private internal projects, my organization is developing a social network and we would like to offer support to users of the system. I assumed that the using public projects through the API was the solution, but if they are going away I'd like to know if there is another solution.

I did see a few mentions of "Tender" and it said that Lighthouse users get a discount, but I didn't see what the discount is.

Lastly, my organization is a non-profit and I'd like to find out if you have non-profit rates.

  1. 1 Posted by Will Duncan on 21 Apr, 2009 04:07 PM

    Will Duncan's Avatar

    Hey Matt. We do have plans to reorganize the Lighthouse plans in the future and chances are that public projects will be phased out.

    Lighthouse does function as support for some of our users, but if you are working on a social networking app then something like http://tenderapp.com is what you want for your users. Lighthouse does not allow for anonymous commenting or non-user submitted emails. Lighthouse will act as a great primary tool for developers to keep track of what is needed from support, which is why we built Tender and did the Lighthouse integration.

    You get 15% of your Lighthouse plan applied to your Tender account.

    As far as the non-profit goes, we've usually handled that on a discounted yearly subscription with former non-profit organizations who were using Lighthouse. We're still working on Tender as it is very young, but I will get back to you later today with that information. Just let me know what you are looking for specifically.

  2. 2 Posted by Virgil Dupras on 02 Jun, 2009 10:14 AM

    Virgil Dupras's Avatar

    I am trying Lighthouse and so far I like it. However, the fact that you plan to phase out public projects unsettles me. What are the requirement to create an "Open Source" project? Must the source of the project be OSS compliant? Would a project like E Text Editor (http://e-texteditor.com/blog/2009/releasing-the-source) be appropriate for an "Open Source Project" (The guy took a BSD license and added a clause that shareware limitation code must not be tampered with)?

    I'm considering (only considering!) a similar move, and I'm afraid that if I went on with such a move, I couldn't use Lighthouse anymore.

    Also, even if Public project were kept in, isn't the user limit way too low for this type of project? Couldn't there be a distinction between a "developer user" and a "bug submitter user"?

  3. 3 Posted by Rick on 04 Jun, 2009 01:25 PM

    Rick's Avatar

    Yes, E-Text Editor is fine. There are a lot of duplicate licenses out there, and our limitation on the licenses is to prevent the use of redundant licenses. However, it's not really displayed anywhere on the site AFAIK, so you can just pick something approximate.

    Public projects can have unlimited bug submitters, as long as they have Lighthouse user profiles. Open source projects can also have unlimited project members.

    We're only phasing out non-OSS public projects. Lighthouse isn't really designed to function as a general purpose support tool. We used to use it for Lighthouse support, but it's messiness lead to our development of Tender Support (which has an unlisted OSS plan too).

Discussions are closed to public comments.
If you need help with Lighthouse please start a new discussion.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac