Difference between revisions of "Spread the word"
| Line 1: | Line 1: | ||
| + | __NOTOC__ | ||
[[Category:General]] | [[Category:General]] | ||
Do you love Eiffel? Think Design by Contract is the best way to get programs right? Feel unable to live without multiple inheritance, genericity, once routines, agents, conversions, anchored types and other beautiful Eiffel mechanisms? Use EiffelStudio for seamless development of powerful systems, from analysis to design, implementation and maintenance? Revel in the productivity gains? | Do you love Eiffel? Think Design by Contract is the best way to get programs right? Feel unable to live without multiple inheritance, genericity, once routines, agents, conversions, anchored types and other beautiful Eiffel mechanisms? Use EiffelStudio for seamless development of powerful systems, from analysis to design, implementation and maintenance? Revel in the productivity gains? | ||
| Line 4: | Line 5: | ||
If you think the rest of the world should be using Eiffel too, there are many ways to help spread the technology. A few are listed here; of course you are welcome to add others to this list. | If you think the rest of the world should be using Eiffel too, there are many ways to help spread the technology. A few are listed here; of course you are welcome to add others to this list. | ||
| − | + | ==Communicate your excitement== | |
:* Blog about what you do with EiffelStudio. If you don't have a blog yet, you may create one on [http://www.eiffelroom.org eiffelroom.org]. | :* Blog about what you do with EiffelStudio. If you don't have a blog yet, you may create one on [http://www.eiffelroom.org eiffelroom.org]. | ||
:* Post on non-Eiffel mailing lists, especially when you see people encountering an issue nicely solved by Eiffel. | :* Post on non-Eiffel mailing lists, especially when you see people encountering an issue nicely solved by Eiffel. | ||
| Line 12: | Line 13: | ||
:* Present your Eiffel-based work at technical conferences. | :* Present your Eiffel-based work at technical conferences. | ||
| − | + | ==Help develop the community== | |
:* When new users post questions to the EiffelStudio Developer mailing list or other forums, answer with constructive suggestions. | :* When new users post questions to the EiffelStudio Developer mailing list or other forums, answer with constructive suggestions. | ||
:* When users post requests for help, e.g. with a program that doesn't work, provide technical help. | :* When users post requests for help, e.g. with a program that doesn't work, provide technical help. | ||
| − | + | ==Help make the Eiffel story well represented in the forums that matter to developers== | |
:*Subscribe on [http://freshmeat.net/projects/eiffelstudio Freshmeat] to the new releases of EiffelStudio. Do not forget to cast your rating of EiffelStudio. | :*Subscribe on [http://freshmeat.net/projects/eiffelstudio Freshmeat] to the new releases of EiffelStudio. Do not forget to cast your rating of EiffelStudio. | ||
:*Also enter your rating fpr [http://www.gnomefiles.org/app.php/EiffelStudio EiffelStudio on Gnome]. | :*Also enter your rating fpr [http://www.gnomefiles.org/app.php/EiffelStudio EiffelStudio on Gnome]. | ||
| Line 23: | Line 24: | ||
:*Don't forget [http://www.slashdot.org Slashdot]. | :*Don't forget [http://www.slashdot.org Slashdot]. | ||
| − | + | ==Participate!== | |
:*Add Eiffel support to an existing tool. | :*Add Eiffel support to an existing tool. | ||
:*Add a class to EiffelBase and other libraries. | :*Add a class to EiffelBase and other libraries. | ||
| Line 34: | Line 35: | ||
:*Help improve [http://dev.eiffel.com the Eiffel developer's site] (this site). There's always useful information to add and better ways to organize the existing information. | :*Help improve [http://dev.eiffel.com the Eiffel developer's site] (this site). There's always useful information to add and better ways to organize the existing information. | ||
| − | + | ==About style== | |
When you post on forums and lists, ''your comments will reflect on Eiffel''. Make sure to emphasize the benefits that brought you to Eiffel and explain them to newcomers. And always: | When you post on forums and lists, ''your comments will reflect on Eiffel''. Make sure to emphasize the benefits that brought you to Eiffel and explain them to newcomers. And always: | ||
# Be nice. | # Be nice. | ||
# Respect other people and their opinions. | # Respect other people and their opinions. | ||
# Never flame anyone. | # Never flame anyone. | ||
Revision as of 15:04, 7 August 2007
Do you love Eiffel? Think Design by Contract is the best way to get programs right? Feel unable to live without multiple inheritance, genericity, once routines, agents, conversions, anchored types and other beautiful Eiffel mechanisms? Use EiffelStudio for seamless development of powerful systems, from analysis to design, implementation and maintenance? Revel in the productivity gains?
If you think the rest of the world should be using Eiffel too, there are many ways to help spread the technology. A few are listed here; of course you are welcome to add others to this list.
Communicate your excitement
- Blog about what you do with EiffelStudio. If you don't have a blog yet, you may create one on eiffelroom.org.
- Post on non-Eiffel mailing lists, especially when you see people encountering an issue nicely solved by Eiffel.
- Write to the press about how you solved programming challenges with EiffelStudio.
- Contact Eiffel Software to add your success story or testimonial.
- Give Eiffel talks at your company.
- Present your Eiffel-based work at technical conferences.
Help develop the community
- When new users post questions to the EiffelStudio Developer mailing list or other forums, answer with constructive suggestions.
- When users post requests for help, e.g. with a program that doesn't work, provide technical help.
Help make the Eiffel story well represented in the forums that matter to developers
- Subscribe on Freshmeat to the new releases of EiffelStudio. Do not forget to cast your rating of EiffelStudio.
- Also enter your rating fpr EiffelStudio on Gnome.
- Subscribe to EiffelStudio on Ohloh and give kudos to your favorite EiffelStudio developers.
- A site for programming language enthusiasts, which could use more Eiffel material, is Lambda the Ultimate.
- Don't forget Slashdot.
Participate!
- Add Eiffel support to an existing tool.
- Add a class to EiffelBase and other libraries.
- Contribute a new library.
- Contribute or improve EiffelStudio or library documentation.
- Provide or improve an internationalized version of EiffelStudio for a language you know (see the translator page to find out who is already working on international versions, and for the link to internationalization instructions).
- Add a facility to EiffelStudio. Yes, it's 2 million lines of code, but its Eiffel code and not as formidable as it sounds!
- Provide your feedback on new versions (EiffelStudio has two releases a year, Northern Spring and Southern Spring and things are moving quickly).
- To help prioritize requests for evolution, provide feedback on the EiffelStudio roadmap and the language roadmap (which contains the plan for implementation of the advances of the ISO/ECMA standard).
- Help improve the Eiffel developer's site (this site). There's always useful information to add and better ways to organize the existing information.
About style
When you post on forums and lists, your comments will reflect on Eiffel. Make sure to emphasize the benefits that brought you to Eiffel and explain them to newcomers. And always:
- Be nice.
- Respect other people and their opinions.
- Never flame anyone.
