I'm new to Smalltalk, I did the Inria MOOC and really like the way of how to construct applications. Still I wonder how development teams approach development with Pharo.
Currently I'm thinking of implementing a small idea of mine with Pharo since Seaside felt quite nice when I experimented a bit. The project would need to be open source because I want to apply for funding at a initiative that only supports open source projects. But then I don't have the feeling that the Monticello approach is the most inviting way to get funding or contributors considering everyone is used to Github. I found now the guide to Git with Pharo by Peter Uhnak (thanks for writing that post!) so maybe this would be a good solution... Searching for best practices I read about some projects that make sure developers always get a new image every day, how could that be implemented without too much hassle of needing a server with some kind of build system. *tl;dr*: how could and should I approach the development of an open source project with Pharo, considering acceptance of Monticello usage and sharing of pharo images? -- View this message in context: http://forum.world.st/What-are-the-best-practices-for-an-open-source-project-with-Pharo-tp4915559.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
