Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I've been doing a lot of research into what blogging software I should use to set up my personal website. I've developed themes in WP, before, and really dislike the way it's set up. It's just so messy, and feels like I'm always working against the software whenever I try to do anything.
So far, Movable Type is looking like a great alternative, but I'm not sure if I want to go with the open source or pro version. I can't find any definitive literature on the subject, or satisfactory comparison of the two services. I'd like to build my website from the ground, and have it running with as little fuss, and as little bloat as possible. Which have you gone with, if any? What are the major differences between them?
I use Movable Type Pro for most blog and web CMS applications, and recommend it to my company's customers.
The differences between Movable Type Pro and Movable Type Open Source are that Movable Type Pro includes:
1) Custom fields, which are discussed briefly in http://www.movabletype.org/documentation/professional/custom-fields/overview.html. Custom fields are one of the key tools in the arsenal of a professional Movable Type consultant.
2) Social Networking features represented by the Movable Type Community Solution. This is discussed extensively in http://www.movabletype.org/documentation/community/. The Community Solution is a product that has been part of Movable Type Pro since 2008. It does not provide integration with Facebook, Twitter, and other social networks. What it provides is the ability to construct a private community of users of your Movable Type-based website.
I have used Movable Type Community Solution by installing it and customizing the look and feel by CSS overrides. But I think the greatest value of the Movable Type Community Solution to a web developer in 2012 is being able to look at the code and see how the features are constructed. I have learned a great deal about Movable Type professional template coding and application construction by setting up a Community Solution-based website on my localhost and breaking down the templates associated with the Community Solution.
There are many other sources of valuable Movable Type solutions and techniques that are freely available on Github. The largest of these repositories is https://github.com/movabletype/, but there are others maintained by third party development companies and individual developers.
Most of these plugins, template sets, and themes will work with either Movable Type Pro or Movable Type Open Source.
The MT-plugin Field Day (can be used in the OS version) is a good alternative to Custom Fields (Pro version).
Your biggest challenge is choosing between MT4 and MT5 I guess.....
The ProNet might be helpfull on that: http://ml.sixapart.com/mailman/listinfo/pronet
The difference with MT OS and MT Pro is mostly Custom Fields, which is a really powerful feature if you want to use MT as a custom CMS:
http://www.movabletype.org/documentation/professional/custom-fields/overview.html
The pro version also bundles a set of nice looking themes:
http://www.movabletype.org/documentation/professional/professional-website.html
I like Movable Type because it doesn't try to do too much for you if you already know html + css. The biggest pain is continually rebuilding everything to generate static files. The upside to this is that your website will never crash with sudden surges in traffic, as WP blogs often do.
I haven't tried textpattern.
I use Pro on several enterprise sites. The support was the main reason for going that route. The Pro package comes with a number of Community and Corporate templates if you want to take advantage of them. However, you could probably do much the same with the open source version if you wanted...it might be a bit more effort.
I love MT. You can make a site template and plug MT into the background to maintain everything. I use it mostly as a CMS, not a blog.
You should know that MT PRO contains two packages more than MT OS.
The two packages are called:
Professional Pack
Community Pack
The 'Professional Pack' introduces the custom fields feature which you could indeed compensate with the 'Field Day' movable type plugin available at: https://github.com/movabletype/mt-plugin-field-day.
However, while the 'fields day' plugin wasn't revised in the last 3 years, the movable type custom fields feature is improved on an ongoing basis and I'm proud to have contributed myself with a few bug reports.
The 'Community Pack' allows you to turn your website into an online community where users could register, sign in, have a profile, follow and be followed.
Both PRO packages are introducing a few more default template sets which allow you to build professional websites, professional blogs, community blogs and community forums.
The license cost is affordable for companies and there is also a free license for individual bloggers.
Upgrading from OS to PRO is could be done just like any other regular upgrade.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
Straight to the point: What is the best method to make an interactive website with a database connection? My current path is to code it all by myself (cue the song). How would you tackle this situation with today’s methods and possibilities?
I already have read into HTML5 and CSS3. I’ve “finished” the homepage with html and wrote the main-css (here is the fiddle).The sections on the frontpage should contain elements from the database in the future. The bacon ipsum is just an inadequate place-holder. :P
<section>
<h2>Newest entries</h2>
<p>Bacon ipsum ....</p>
Currently I’m looking at JS, JQuery and PHP but it’s all relatively new to me. During my studies we looked at JavaEE but I’m unsure if it’s the right approach for this. The attached diagram shows what classes my website should support. The website should enable collaborative writing of stories between multiple people.
What I would like to know is: Which is the best way to create a functional site? I know one option is to code it all by myself but I have a very strong feeling that all the functionality which I need is already available. Could someone give me a nudge in the right direction?
My hosting-provider supports MySQL 5, subdomains, Website Redirect, Cronjobs, Domain Mapping in root, Website Directory Indexing, PHP 4, PHP 5 mit SOAP Support, Perl, Python, RealAudio, Ruby 1.8.7, ImageMagick, Ghostscript, Zend Optimizer, Gd
The provider also offers following 1-click installations:
WordPress, Joomla, Concrete 5, bbPress, BuddyPress, Drupal, phpBB2 & 3, Elgg Social Network System, MODX, Vanilla Forums, Pligg Social Networking, Moodle, CMS Made Simple, Piwik, Simple Machines Forum (SMF), Zenphoto, StatusNet, LimeSurvey. MantisBT, PHProjekt, Pixelpost, phpMyFAQ, Textpattern,Open Web Analytics, Geeklog Blog, Nucleus Blog, Mambo CMS, Locked Area Lite Password Manager, Eblah Online Discussion Forum, TYPO3 Content Management System, Crafty Syntax Live Help, phpCoin Web Hosting Billing System, Revive Adserver, dotProject - Project Management, osTicket - Ticket System, Postcards,Form to Email with CAPTCHA, Custom 404 and 500 Error Pages, Search Engine, Free For All Links page, Banner Advertising System, Online Auction - Just Like eBay, Domain Name Checker, Coppermine Online Photo Gallery, Web Calendar, Web Survey, Gallery2, RoundCube Webmail, MediaWiki, SugarCRM
Looking forward to your recommendations.
I have used Drupal and build some sites with it. It's really powerful and there are a lot of free modules you can use. I'm not sure if there is a module to write collaborative content, but maybe you can tune the workflow module. Anyway if you need it you can code a new module by yourself, but only for the specific functionality you need.
Drupal is very modular and simple, obviously it has a learning curve but I think it is not very hard and it is well documented.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
If the specifics are important, I made a cruisecontrol.net publisher plugin that notifies a series of phone numbers via voice, announcing the current state of the build. It uses Twilio to do so.
I'd like to avoid getting hung up on the specifics of what it is I've made, as I have this question a lot, with a number of little hobby one-offs. What's the state of the art as far as making my hobby output available to the world at large?
There seem to be a lot of options for open-source project hosting, community features, and what role to take in all of this. It's a little bewildering. What I'm looking for is to put this out into the wild for free and basically take a hands-off approach from there. Is that realistic? Which project hosting service can I use for free to allow developers to at least download the code, report issues and collaborate with each other to improve the product?
What snags have you run into that could make me regret this decision? I'm interested in war stories, advice and guidance on making this little product available to the community where it can be used.
GoogleCode is a decent self repository for open source code. Very easy to use and contains the ability to create a wiki for the project. It also has a very easy to use and understand bug reporting/forum style issue management system.
One easy way to quickly get code on a publicly accessible host is github.com. Hosting is free if everything you host is available to the public. People would be able to grab latest, and notify you when they have updates they think are worth merging.
You would include documentation as a README.
CodeProject is cool, sites like that would allow more community discussion then what I've seen on Github.
If it's just a small example, or a small piece of code, you might think about just posting an ariticle on a site like "Code Project", or a blog.
There's a lot of overhead with releasing an open-source project, and if you want to be hands-off, you might have an easier time just writing an article, and providing a .zip to download the code example.
Take a look at SourceForge.net, which is a website where programmers can create their open-source projects. It allows you to add new users which may have different rights on your project (from just being a contributer to being a full administrator) and it features many tools which you might want to use for your project, such as a bug tracker and SVN.
CodePlex is another good place for posting projects. There's lot's of C#/.NET there. In addition to all the basic project hosting stuff one of the nice things about it is that they support a whole slew of source control clients.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I currently have a few closed-source applications that I have developed to learn a particular technology or experiment with a programming technique. As a result, I have some software that is useful to others and that I have made freely available, but in closed-source format.
Some of the users of the software have asked if I would be willing to go open-source with the software so they could contribute to it. I'm all for it, but haven't had any previous experience working on open-source projects, much less starting one.
Ideally I'd get my feet wet by contributing to an existing project first, but I don't want quell enthusiasm of these volunteers by delaying too long. So I am going to forge ahead slightly blindly.
What I am looking for is a crash-course in managing an open-source project for someone just starting out on this track.
So let me phrase this as a question:
What advice do you have for someone
starting up their first open-source
project?
I'm also interested in recommendations for books/links that you think would be helpful
You have two important choices to make initially.
Firstly which licence should you use? There are dozens of Open Source licences, but it basically boils down to whether you want copyleft (GPL/AGPL) or non-copyleft (BSD, MIT, Apache) and that depends on your own objectives.
Secondly, you need to choose a version control system and, assuming you won't be hosting it yourself, a provider. This is effectively a choice between Subversion or one of the distributed version control systems (Git, Mercurial, Bazaar, etc.). A DVCS may make it easier for you to manage contributions from other people if you don't want to give them write access to your master repository.
Choice of VCS will influence your choice of host and vice versa as most providers only offer one VCS. A provider that will also host a website and/or wiki for you would be ideal. Most will provide some kind of rudimentary issue tracker and possibly mailing lists. You can also get mailing lists from Librelist.
I would recommend that you take a look at GitHub or Launchpad. I'm not particularly keen on Google Code or Sourceforge. Nothing against Subversion, I just don't like their UIs.
If you want your project to become popular, and that might not be important to you, you'll have to promote it. You can register it with Ohloh and Freshmeat. Writing blog articles about your project and submitting them to sites like Reddit and DZone would increase visibility. Remember also that Jeff is offering free advertising on StackOverflow for Open Source projects.
Anyway, as long as you have a public source repository and a website for people to download the software from, just write code and the rest will follow.
If you're already familiar with VCS (Versioning Control System) you should be fine. I recommend www.github.org to host the repository, and maybe at some point a website to talk about the app. Github is nice because it makes it especially easy for people to contribute code. It's ridiculously simple, although git has a bit of a learning curve.
And then, a way to communicate! A mailing list.. Maybe googlewave.. Maybe a forum.
Don't miss the great e-book from Karl Fogel, Producing Open Source Software available at no cost online.
I don't have any personal advice on hand, but I found the following video very interesting. It's a recollection of the experiences of some Google employees and the lessons they learned whilst managing their open source projects.
How Open Source Projects Survive Poisonous People (And You Can Too)
https://www.youtube.com/watch?v=Q52kFL8zVoM
Read this book: Wikinomics
In one of the chapters, for example, the author explains the challenges faced by IBM when they first joined open source projects on Linux.
Some code repository sites do a lot of the management work for you. They provide the licenses, they handle versioning (in some cases) and they obviously handle the repository.
look at these sites:
http://www.codeplex.com/
http://www.codeproject.com/
http://sourceforge.net/
The very minimum that you need to do is post the code as a zip, with a suitable license file. You can do that at Google Code - it's really easy to use. As for which license, start with an unrestrictive one such as MIT (Google Code has all the license texts) - you can always re-license later, provided you haven't accepted any updates.
As for books/links, take a look at Producing Open Source Software - it's not perfect, but I don't know of anything better.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
First of all, I reviewed this question, but I think I need a little more information since I've never worked on an opensource project before.
I'm starting an opensource project, currently hosted on Google code. It is a framework for creating flash games in ActionScript3 (programmer oriented). So far, so good, but I want to start building a community around it. The project is 60% finished from it's first official stable release (I am using Scrum to guide the development process, currently we are 3 people on the development team). By the way, the project has the MIT licence.
Do you have any advice on how to guide the development, any tools that I should look at?
Assembla vs Google code vs Trac vs Pivotal tracker?
What are you experiences on this?
If you're looking to build a community, it's not always about the tools, more about the processes you can use to build a community. There are plenty of people who will use whatever tool you give them or will choose (or refuse) to participate in a project based on the tools, but if the community stinks very few people will hang around.
I'd recommend spending some time thinking about how you're going to embrace a community. Are you ready to take the time to respond to bug reports? How will you handle enhancement requests? Are you willing to let something into the code if several people want it, but you don't? These are all critical issues that in the end will be far more important then Assmebla vs Trac.
You may want to check out Karl Fogel's book Producing Open Source Software or Jono Bacon's The Art of Community for more hints on managing and building a community.
First, big obvious download buttons so that a person can download your project, make it just plain easy. Secondly, forums so that people can give you feedback good and bad about the project.
Good luck on your project!
I would suggest checking out this book: http://producingoss.com/
I believe there is a free online and pdf version.
I have messed around with Trac some and it can certainly get the job done but if you are already doing an agile development process I would check out Pivotal Tracker. I use it on a side project and it's pretty slick, not to mention free to use. Pivotal has all the things you would expect: stories, backlog, velocity calculation, a few charts, etc.
Strive for adoption. The more users you get, the more people will contribute back.
Include lots of code samples on the wiki and let users download a sample application.
Make sure your API is well-documented with ASDoc.
Provide a roadmap to so that potential users can see your direction and intentions.
Be diligent about prioritizing feature requests and bugs. You and your team don't have time to do everything.
Make integration as seamless as possible. Hopefully users will be able to simply download a .swc (Flash library) and link it into their application.
Release early, release often. I hate having to download and use the HEAD revision from a repository because a team has only officially released one version of their project and it's a year old.
To me, guiding the development is more a matter of prioritizing what has to be done so I'm tempted to say: why don't you just use Google Code issue tracker as your project is already hosted there? I think it's offering all you need. Customize it to add a Estimates field if you want (for Scrum) and there you go.
Why do you think you would need something else? You already have a source repository, code reviews facilities, a wiki, mailing lists, an issue tracker, secured access for contributors. You don't need much more for collaborative work. What are you missing? Instant Messaging? Use Skype or Gtalk. IRC? You don't need it for now. No, really, I don't think a tool is gonna solve anything more here (even if you can't draw your burndown chart, not a big deal for a non full time project IMO).
So, because any other tool would be less well integrated with other Google Code services (e.g. I like to link my commits to issues using "Issue #ID" in comments which is automatically linked), I'd stick with what you currently have (maybe just add Gtalk/Skype to ease the communication/collaboration) and I'd start creating issues and prioritizing them. Good prioritization of work is the key to a successful project, there is no silver bullet tool that will do this for you. Then, plan fixed date milestones (releases) and assign most important issues to the upcoming milestone. Close as many issues as you can before the deadline. When the release time has come, release what has been done, postpone non implemented issue to the next milestone and start again.
If you need a software to support your scrum project... agile42 offers free Licenses of Agilo for Scrum Pro for open source projects.
Don't host your code on codeplex. I recently started an open source project as the basis of an article series on DotNetSlackers.com to show people how to build a site like SO. I mistakenly hosted this project on CodePlex. My automated build will periodically send me broken build emails as CodePlex will randomly go down for hours at a time. IT DRIVES ME NUTS!
If you plan to develop code that is free to the world but don't plan on letting anyone and everyone submit code to your project...host your own source control (perforce is free for a couple of users) or use something like google to host your code.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
I'm looking for a free/open source collaborative project manager that can be deployed internally in my workplace that would act similar to Codeplex or Sourceforge. Does anyone know of something like this, and if so do you have experience with it.
Requirements:
Open Source or Free
Locally Deployable
Has the same types of features found in Sourceforge / Codeplex
Issue/Feature Tracking
Community Interaction (ie. Voting, Roles, etc.)
SCM Integration (Optional)
.NET/Windows Friendly (Optional)
Every business ends up having internal utilities, and domain specific apps that developers create to make life easier. Given the input of the internal developer community they have the potential to become much better (can you say GMail...), and I would simply like to foster such an environment internally by providing an easy place for that interaction to take place.
UPDATE:
So I like what I am seeing in both Trac and GForge, but both are heavily geared towards UNIX/Subversion environments. I should have specified this, but we are a MS shop from top to bottom. How practical do you think it is going to be to try and use these in a MS .NET environment? Would that be like trying to shove a square peg through a round hole?
I like redmine for this: http://www.redmine.org. The only thing it's missing from your criteria is voting, but there might even be a plugin for this.
Trac is also popular (http://trac.edgewall.org) but it lacks suport for aggregation of data across projects.
Try GForge, it's a SourceForge fork and has most of its features.
I agree, Trac should work. IMHO setting up Subversion should be relatively easy on Windows too, there are great Windows clients for it (tortoiseSvn), and Trac runs on python, so it will work on Windows too.
Other advantages of Sourceforge Enterprise are these plugins. There are extra plugins for Visual Studio wich can be found here and here.
SourceForge Enterprise Edition 4.4 is available for free for up to 15 users. We use it for our development team and another development team where I work.
It's been working great for us. It has subversion and cvs built in (whichever you wish to use). If you plan on accessing it over the internet you might want to enable HTTPS. I had to do a little finagling to get HTTPS to work correctly (finding the right CentOS packages to install). If you wanted to use this solution with HTTPS I wouldn't mind if you sent me a message asking for help.
It comes with a VM for VMWare Player:
http://www.collab.net/downloads/sfee/index4.4.html
Launchpad has support for Code Hosting and version control, Bug tracking, Blueprints, Answers, Polls, Translations, etc.
Launchpad is used by the Ubuntu Project.
A few weeks ago, Launchapad was released as open source.
I was just wondering the same thing, something like Trac but in .NET, after a quick GOOGLE search (I have never tried these tools) I found
sharpforge (This no longer looks free!)
I like how the site .netTiers looks.
They use screwturn wiki.
It is totally free if you fulfill all GPLv2 statements.
Assembla and BeanStalk are nice, both have things like; wiki, discussion, alerts, chat, ticketing, Trac, Git and Subversion
What about Trac? It's pretty simple, but does it's Job for a lot of Open Source projects.
I would concur on the Trac suggestion. I use it both for an open source project and for an internal project. It has decent issue tracking and integration with Subversion which allows links between tickets and subversion checkins. It also has an integrated wiki, which can be of some use for documentation. Although we do not use it for voting / community type features, I know there's a number of addons to it that might serve this purpose.