Home     |     Java    |     Php General    |     Oracle Database    |     Oracle Server  

MS Dynamics CRM 3.0

  •  Setting up and Configuring Microsoft Dynamics CRM 3.0
  •  Managing Security and Information Access
  •  Entity Customization: Concepts and Attributes
  •  Entity Customization: Forms and Views
  •  Entity Customization: Relationships, Custom Entities, and Site Map
  •  Reporting and Analysis
  •  Workflow
  •  Server-Side SDK
  •  Client-Side SDK
  •  Integration with External Applications
  • Cervo Technologies
    The Right Source to Outsource

    Sharepoint Portal Server KB

    Microsoft CRM Info

    WPF Interview Questions

    SilverLight Interview Qs

    Asp.Net 2.0 Interview Qs

    Asp.NET 1.1 FAQs

    Oracle Interview Questions

    SAP Interview Questions

    PHP Programming

    Making code public -- What steps to take? GPL?


    Micky Hulse wrote:
    > Or, should I just not worry about this?

    Well shux! I love it when I answer my own questions:

    <http://www.phpfreaks.com/tutorials/19/0.php>

    I blame it on lack of sleep!

    The GNU GPL License sounds like what I need. :D

    Cheers,
    M

    --
    Wishlists: <http://snipurl.com/1gqpj>
        Switch: <http://browsehappy.com/>
          BCC?: <http://snipurl.com/w6f8>
            My: <http://del.icio.us/mhulse>

    Hi,

    I am in the process of writing a simple but useful plugin for a blogging
    application....

    Long story short, I want to give-back to the community (i.e. free
    plugin), but would like to make an attempt at retaining some credit if
    folks port/use to/in other scripts/blogs/cms apps.

    Any tips or links ya'll could share with me?

    Anyone have any /* comment blocks */ I could put in my code?

    Something like this, for example:

    /*
    ** THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY
    ** OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT
    ** LIMITED   TO  THE WARRANTIES  OF  MERCHANTABILITY,
    ** FITNESS    FOR    A    PARTICULAR    PURPOSE   AND
    ** NONINFRINGEMENT.  IN NO EVENT SHALL THE AUTHORS OR
    ** COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES
    ** OR  OTHER  LIABILITY,  WHETHER  IN  AN  ACTION  OF
    ** CONTRACT,  TORT OR OTHERWISE, ARISING FROM, OUT OF
    ** OR  IN  CONNECTION WITH THE SOFTWARE OR THE USE OR
    ** OTHER DEALINGS IN THE SOFTWARE.
    */

    Different verbiage, of course...

    Or, should I just not worry about this?

    Lol! I hope I am phrasing my question right... I have been up all night
    coding, so my brain is kinda mushy right about now. :D

    Many TIA's!
    Cheers,
    Micky

    --
    Wishlists: <http://snipurl.com/1gqpj>
        Switch: <http://browsehappy.com/>
          BCC?: <http://snipurl.com/w6f8>
            My: <http://del.icio.us/mhulse>

    -----------------------------------------------Reply-----------------------------------------------

        If you want to retain some credit but don't care about
    distribution/modification/redistribution, check out the MIT license (more
    commonly referred to as the X or X11 license).  We're using it in a project
    that combines PHP and text-to-speech technology.  It allows people to
    improve (or degrade) our code, but says that we should still get our names
    at the top as the original authors.

    On 5/13/07, Micky Hulse <m@ambiguism.com> wrote:

    --
    Daniel P. Brown
    [office] (570-) 587-7080 Ext. 272
    [mobile] (570-) 766-8107

    -----------------------------------------------Reply-----------------------------------------------
    On 5/13/07, Daniel Brown <paras@gmail.com> wrote:

    >    If you want to retain some credit but don't care about
    > distribution/modification/redistribution, check out the MIT license (more
    > commonly referred to as the X or X11 license).  We're using it in a project
    > that combines PHP and text-to-speech technology.  It allows people to
    > improve (or degrade) our code, but says that we should still get our names
    > at the top as the original authors.

    You know more than me daniel :P

    All current releases aren't packed with any license, and in
    sourceforge the PHP license is selected i believe :P

    I'd say, don't worry too much about the license, just put your name on
    top of the code, and some other nonsense, like:
    You're allowed to use this code, as long as you leave above lines
    intact., where above your credit is listed of course.

    Tijnema

    Daniel Brown wrote:
    >    If you want to retain some credit but don't care about
    > distribution/modification/redistribution, check out the MIT license (more
    > commonly referred to as the X or X11 license).  We're using it in a project

    Ah, great tip! :D

    I will definitely read-up on the MIT license after I get some zzZZzz's!

    It sure does sounds like what I am looking for. ;)

    > that combines PHP and text-to-speech technology.  It allows people to
    > improve (or degrade) our code, but says that we should still get our names
    > at the top as the original authors.

    Oh, wow! That sounds like a great project... and it is cool to hear what
    you/your team decided to use for licensing. :)

    Many thanks Daniel! I really appreciate the help and advice.

    Have a great day,
    Cheers,
    Micky

    --
    Wishlists: <http://snipurl.com/1gqpj>
        Switch: <http://browsehappy.com/>
          BCC?: <http://snipurl.com/w6f8>
            My: <http://del.icio.us/mhulse>

    -----------------------------------------------Reply-----------------------------------------------

    Hey! Tijnema! Thanks for the quick reply. :)

    Tijnema ! wrote:
    > I'd say, don't worry too much about the license, just put your name on
    > top of the code, and some other nonsense, like:
    > You're allowed to use this code, as long as you leave above lines
    > intact., where above your credit is listed of course.

    Ah, well, that does sound good too. I a mainly looking to keep my
    name/website somewhere in the comments. :D

    Whichever route I end-up taking, it is definitely nice to hear what the
    pros prefer. ;)

    Thanks again Tijnema!

    Have a great day.
    Cheers,
    Micky

    --
    Wishlists: <http://snipurl.com/1gqpj>
        Switch: <http://browsehappy.com/>
          BCC?: <http://snipurl.com/w6f8>
            My: <http://del.icio.us/mhulse>

    -----------------------------------------------Reply-----------------------------------------------

    On Sunday 13 May 2007 21:17, Micky Hulse wrote:

    > I will definitely read-up on the MIT license after I get some zzZZzz's!

    Don't forget the MIT license allows people to incorporate your code into
    commercial products and sell for profit without having to give anything
    back (money/improved code/etc).

    --
    Crayon

    -----------------------------------------------Reply-----------------------------------------------

        Right, I alluded to that, but perhaps I should've said that exactly, as
    it may bother some people.  In my case, it doesn't bother me in the least,
    just as I use LAMP (all open source) to make a living.

    On 5/13/07, Crayon Shin Chan <crayon.shin.chan@gmail.com> wrote:

    --
    Daniel P. Brown
    [office] (570-) 587-7080 Ext. 272
    [mobile] (570-) 766-8107

    -----------------------------------------------Reply-----------------------------------------------

    Crayon Shin Chan wrote:
    > Don't forget the MIT license allows people to incorporate your code into
    > commercial products and sell for profit without having to give anything
    > back (money/improved code/etc).

    Hi Cayon, thanks for clarification.

    I just woke up, so I have not had a chance to really research the best
    option for my code... Hmm, a part of me does not mind the things you say
    above, but another part of me wonders if it would be best to restrict
    the commercial usage of it.

    Heheh, well, either way, thanks for the help. I appreciate it.

    Have a great day.
    Cheers,
    Micky

    --
    Wishlists: <http://snipurl.com/1gqpj>
        Switch: <http://browsehappy.com/>
          BCC?: <http://snipurl.com/w6f8>
            My: <http://del.icio.us/mhulse>

    -----------------------------------------------Reply-----------------------------------------------

        The biggest thing to remember is that a license is like a key.... it's
    meant to keep an honest man honest, but won't stop someone who is intent on
    taking what they want for a profit.

    On 5/13/07, Micky Hulse <m@ambiguism.com> wrote:

    --
    Daniel P. Brown
    [office] (570-) 587-7080 Ext. 272
    [mobile] (570-) 766-8107

    -----------------------------------------------Reply-----------------------------------------------

    Daniel Brown wrote:
    >    Right, I alluded to that, but perhaps I should've said that exactly, as
    > it may bother some people.  In my case, it doesn't bother me in the least,
    > just as I use LAMP (all open source) to make a living.

    Oh, I think I understood that. But there is always room for
    clarifications. :D

    Thanks Daniel,
    Cheers,
    Micky

    --
    Wishlists: <http://snipurl.com/1gqpj>
        Switch: <http://browsehappy.com/>
          BCC?: <http://snipurl.com/w6f8>
            My: <http://del.icio.us/mhulse>

    -----------------------------------------------Reply-----------------------------------------------

    Beware also that if you have an "advertising clause" that requires your name
    to stay on it, then you could be preventing GPLed projects from using it.  
    The GPL is incompatible with "advertising clause" licenses.  That's why the
    PHP License, for instance, is GPL-incompatible.  (GPL is the most widely used
    Free Software / Open Source license by a very wide margin.)

    If you're OK with both open source and proprietary usage, then consider the
    LGPL.  It's compatible both directions, only requiring modifications to your
    code specifically to be shared.  The modern BSD license is even more
    permissable.  It doesn't have a mandatory advertising clause, but IME if you
    have a good drop-in module that has a "copyright Me and released under the
    LGPL, see home page here" type message most people won't bother taking it
    out.  

    The people who would try to take credit for your code wouldn't care what
    license it was under in the first place anyway.  

    Thank you for sharing your code!

    On Sunday 13 May 2007, Daniel Brown wrote:

    --
    Larry Garfield                  AIM: LOLG42
    l@garfieldtech.com           ICQ: 6817012

    "If nature has made any one thing less susceptible than all others of
    exclusive property, it is the action of the thinking power called an idea,
    which an individual may exclusively possess as long as he keeps it to
    himself; but the moment it is divulged, it forces itself into the possession
    of every one, and the receiver cannot dispossess himself of it."  -- Thomas
    Jefferson

    -----------------------------------------------Reply-----------------------------------------------

    On Monday 14 May 2007 07:30, Daniel Brown wrote:

    Please don't top post.

    >     The biggest thing to remember is that a license is like a key....
    > it's meant to keep an honest man honest, but won't stop someone who is
    > intent on taking what they want for a profit.

    Sure, but if you don't make your intentions clear from the start then
    there's no use complaining afterwards. Not quite an accurate analogy but
    here goes:

    "If you leave valuables around your house and leave the doors and windows
    unlocked you're not going to get much sympathy from the police (or the
    insurance company for that matter) when you get burgled."

    So, if you don't use a suitable license then you don't have a stick to
    beat someone with should it ever come to it.

    --
    Crayon

    -----------------------------------------------Reply-----------------------------------------------

    Howdy,

    I just wanted to say, to all who responded, many many thanks for the
    help. I greatly appreciate it. I have not made my decision just yet, but
    it has been great hearing the advice and reading about all the different
    options available... Well, anyay, thanks! This list has been a life
    saver. :)

    Cheers,
    Micky

    --
    Wishlists: <http://snipurl.com/1gqpj>
        Switch: <http://browsehappy.com/>
          BCC?: <http://snipurl.com/w6f8>
            My: <http://del.icio.us/mhulse>

    Add to del.icio.us | Digg this | Stumble it | Powered by Megasolutions Inc