@terminills

Quote:

I see this. I really hate when people turn a blind eye towards copyright violations when it suits their agenda.

Well, MorphOS supporters should be careful when crying "copyright violation". Last time I checked, MorphOS SDK still contained copy/paste from AmigaOS NDK.

As AROS is safe in this regard, feel free to continue in whatever noble effort you do in this and other threads.

@terminills

That's "extra info". I said badges.

Source

In other words, to avoid people constantly having to explain who someone else is....
What would be wrong with having badges for AROS, MorphOS, Classic developers?

By virtue of having explicitly labelled forums here for AROS, MorphOS, Classic, there's already an admittance that this site supports all, right? So why limit badges? Why not be more informative?

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@pavlor

I thought you are Amiga Inc. fan

Now defending Hyperion all the time

you changed camp?



From openness view I would say it that way... both Hyperion and MorphOS team created closed platforms and are not very interested in open source

at least MorphOS team did follow the rules and gave back sources when they used Aros sources for MorphOS

If AmigaOS ever included Aros sources and if they followed the rules is outside of my knowledge. To be honest I am not aware of any sources Hyperion ever opened

But what we are discussing now anyway?

@pavlor

No, it does not and never did. As has been explained before, the header files in the MorphOS SDK were painfully written from scratch. If you have evidence to the contrary then please come forward and present it. I can assure you that nobody is interested in breaking any copyrights or licences in MorphOS so any mistakes would be rectified immediately.

Besides, trying to defend illegal activities by claiming others do the same is morally worse than questionable.

@Nicho

Quote:

As has been explained before, the header files in the MorphOS SDK were painfully written from scratch.

Read post 206 in this thread (not my analysis).

@pavlor

that is the main problem...

the amiga community is mainly busy to accuse each other bad things than working together (in this thread I include all NG camps) or making lawsuits against each other (like cloanto vs. Hyperion)

That seems to be almost all activity left today

Only fun for attorneys

@number6


oh if we're requesting badges I would like "AROS Troll Extraordinaire" :) But there are a few AROS core developers who should have badges.

Last edited by terminills on 24-Aug-2018 at 04:23 PM.

_________________
Support AROS sponsor a developer.

"AROS is prolly illegal ~ Evert Carton" intentionally quoted out of context for dramatic effect

@pavlor

Yes, I did read that thread and there is absolutely nothing but unsubstantiated allegations in there.

I remember the long discussions we had internally in the team before rewriting those headers as we knew it had to be done eventually allthough it would take a lot of work. Before CISC did that, we could not distribute any OS header files at all with our SDK.

@OlafS25

Quote:

That seems to be almost all activity left today

As you see, nothing really changed since the fall of Commodore. Amiga users need some "enemy"... be it WarpUP vs PowerUP, OS4 vs MorphOS, 68k ultras vs Vampire. But one can´t expect reason from people sticking to more than 20 years dead computing platform.

Last edited by pavlor on 24-Aug-2018 at 04:27 PM.

@terminills

Quote:

oh if we're requesting badges I would like "AROS Troll Extraordinaire" :) But there are a few AROS core developers who should have badges.

It addresses multiple issues.

(1)As I said, it ties with the change in this website over the years to be more inclusive.
(2)In that vein, the owner is a proponent of being inclusive, so he should be in favor of it
(3)It also addresses the constant postings of "sign your posts" or "I wish people would say who they are" that we saw here year after year. That goes with the recent example of you having to tell people who someone else is.
(4)It also (sadly?) addresses the lack of an ignore function on AW to a degree. One could instantly recognize at a glance at a badge, the direction? the post is coming from, and choose to ignore it.

win/win

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@number6

I have to agree with your points. Happy to make these changes.

_________________
Amiga Kit Amiga Store
Links: www.amigakit.com | New Products | A600GS

@amigakit

Quote:

I have to agree with your points. Happy to make these changes.

I realize that doing this with your known Amiga Developers was more easily accomplished.

How do you wish to achieve this with others?

Should developers write to you stating a wish to be included with a badge?
Should they supply any credentials or links that support who they are?

Just thoughts off the top of my head re:procedure

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@number6


I can certainly help with AROS developers as I know of 4-5 off the top of my head who post here

_________________
Support AROS sponsor a developer.

"AROS is prolly illegal ~ Evert Carton" intentionally quoted out of context for dramatic effect

@terminills

You'll have to address this with Matthew.

There may be other questions that spring to mind, like 'are the badges to be done in different colors" or text differences only?

Such opinion might rise depending on the value of my last point. dunno.

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@number6

Badges? We don't need no stinking badges!

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@number6

Not to further veer this thread of course any further, it’s best if they PM me.

_________________
Amiga Kit Amiga Store
Links: www.amigakit.com | New Products | A600GS

I am with @kolla on this, why not use BSD?

My advice to anyone who develop closed source systems is to treat GPL and LGPL code as toxic waste. Just dispose it properly, you do not want it around.

@hth313
I guess you'll start by writing your own C compiler then...?

_________________
MorphOS, classic Amiga, demoscene, and stuff
"When a bridge is not enough, build a Viaduct!"
"Strip the Amiga community of speculation and we can fit every forum on a 720k floppy" (by resle)

@hth313

Quote:

hth313 wrote: I am with @kolla on this, why not use BSD? My advice to anyone who develop closed source systems is to treat GPL and LGPL code as toxic waste. Just dispose it properly, you do not want it around.

My advice would be to read those licenses carefully and understand what you can and cannot do.

My second advice would be: start collecting a shitload of money, you'll need it and you'll probably lose it, if you want to develop an all-closed system these days, and hope that maybe, just maybe, you'll make a dent in the market.

Evert

Last edited by jorit2 on 25-Aug-2018 at 01:09 PM.

_________________
-- Posting for charity -- Investing €10 in a charity related to education or civil rights for every message I post --

@Chain-Q
@jorit2

Just use BSD or similar, read the license and follow it, no problems.

GPL and LGPL are to be disposed in such environment is a minor simplification, but essentially it is true. You can do it, but then you take on following the license and you need to spend time and efforts on doing that. Balance that with the alternatives and you will understand what you want to do. I have been there.

There is nothing wrong with GPL and LGPL, they have their uses, but they do not always make a good fit due to the license.

There is no need to start writing your own C compiler, but if you do, I would recommend looking at Clang (it is not GPL).