How can you delete your account?

1

Hello, all.

Many of you are familiar with my posts which deal with forking Haiku. I won’t get into that… :slight_smile: For a while, I gave up on the idea and pretty much said I’d quit, but I’m going to give it a go–for real this time. :slight_smile:

Anyway, getting to the point–I finally sat down and read the Guidelines, which say once I start building a fork is that I state I’m not associated with the Haiku project. Quote from article: " is not associated with the Haiku project." With that said, how do I delete my Haiku user account (in order to make this statement true)?

I cannot find a link to do this on the page. Any assistance here would be appreciated, guys. The Haiku forum’s been a great community.

2

You will need to contact the forum admin:
https://www.haiku-os.org/user/mmadia

3

Please inform us of your fork somehow though.

4

You may be taking that portion of the guidelines too literally. IIRC, the ‘not affiliated wIth the Haiku Project’ is more to convey to end users that one’s fork (or distro or …) is not Haiku, not assembled by the Haiku Project, etc.

5

I am very sure you’re talking about a distro and not fork.

A fork is you taking the source code one time and then continue developing it how you want. Coding everything yourself or with other developers. This is lots of work and takes a good number of developers.

A distro is you take the source code over & over (from Haiku), make changes and customizations and then release your version of it. One person can do this on their own or with others. Pretty simple.

Senryu is an example of a distro
http://haikuware.com/remository/view-details/utilities/system-system-information/senryu#comment-7477

You should not mix the two up because they mean different things!

Do you intend to copy Haiku source code once and then develop everything in Haiku yourself or with other developers? If no, then you’re not doing a fork.

6

You don’t have to delete your user account. Simply removing the haiku official trademarks and keeping the copyrights should be enough based on the user agreement.

Based on but not endorsed by


Would be sufficient line of thought.
7

Thank you, all.

And most of all, thank you, mmadia, for your post, since I saw that you were the admin I needed to contact. :slight_smile:

@tonestone57: No, I really mean to fork. I’ve mentioned that in two posts I started. I almost quit on the idea because I saw it wasn’t well-liked by everyone. However, I’d like to take the entire kernel, bootloader, installer, apps, icons… everything–and turn it into a new operating system for netbooks from source in compliance to the MIT. (A distribution is the same operating system respun–which is NOT going to be what I’m planning on doing.)

Yes, I imagine it will take months, at the least, to do with a team, or years, individually.

Unlike where Haiku solely focuses on BeOS apps, the fork will focus working with Linux and Windows compatibility as well. It will keep BeOS compatibility, however, It will include a “forked” version of Tracker (which will be most likely named different), a launchable X Window System, Firefox as the default browser (with Cairo), wpa_supplicant, GUI wrapper support for shell scripts (i.e. similar to kdialog), the ufw firewall, a 21st-century icon set that should look halfway photorealistic, plus qemu and Wine installed by default for Windows switchers.

8

[quote=agreimann]Thank you, all.

And most of all, thank you, mmadia, for your post, since I saw that you were the admin I needed to contact. :slight_smile:

@tonestone57: No, I really mean to fork. I’ve mentioned that in two posts I started. I almost quit on the idea because I saw it wasn’t well-liked by everyone. However, I’d like to take the entire kernel, bootloader, installer, apps, icons… everything–and turn it into a new operating system for netbooks from source in compliance to the MIT. (A distribution is the same operating system respun–which is NOT going to be what I’m planning on doing.)

Yes, I imagine it will take months, at the least, to do with a team, or years, individually.

Unlike where Haiku solely focuses on BeOS apps, the fork will focus working with Linux and Windows compatibility as well. It will keep BeOS compatibility, however, It will include a “forked” version of Tracker (which will be most likely named different), a launchable X Window System, Firefox as the default browser (with Cairo), wpa_supplicant, GUI wrapper support for shell scripts (i.e. similar to kdialog), the ufw firewall, a 21st-century icon set that should look halfway photorealistic, plus qemu and Wine installed by default for Windows switchers.[/quote]

I think your making a mess with X. X is a giant mess. I have no idea why anyone would focus on linux compatability. I would focus on windows interoperability.

In fact a great fork could be a deep wine intergration. bringing X brings all the x problems. I wouldn’t do it, microsoft and many other systems get by just fine without that albatross.

9

[quote=agreimann](A distribution is the same operating system respun–which is NOT going to be what I’m planning on doing.)
[/quote]

Ok.

X Windows, FireFox, GUI for shell scripts, newer icons, QEMU & WINE are just add-ons. So, these packages would only make it a distro.

Your changes to Tracker, adding in firewall & wpa_supplicant would change the OS and probably fork it. So I get why you’re saying fork and not distro.

10

Thank you for your input. I’ll consider it.

However, without X, a lot of Linux apps won’t run, and I want to aim for Windows and Linux compatibility. I do know that X has a lot of problems. And, also, I’m thinking of it being “launchable” like X11 on OS X–not to replace the GUI shell with X. :slight_smile:

11

[quote=thatguy]I think your making a mess with X. X is a giant mess. I have no idea why anyone would focus on linux compatability. I would focus on windows interoperability.

In fact a great fork could be a deep wine intergration. bringing X brings all the x problems. I wouldn’t do it, microsoft and many other systems get by just fine without that albatross.[/quote]

Because SDL X can be done fast and easy. That’ll give access to lots of Linux software because the GUIs are done in X and will require minor changes to work with Haiku’s kernel.

Also, with X, he could do WINE using X which would get WINE onto Haiku faster. A native port of WINE will take very long time to happen. So, if someone said they could get you WINE in 6 months but using X would you say yes or would people prefer to wait 3+ years for native version?

I stated in another post that bringing X to Haiku would get software like OpenOffice, WINE, FireFox, VirtualBox, …, onto Haiku the fastest. Of course it’ll get messy and not ideal but it would bring lots more software to Haiku the quickest. It would create a hybrid Haiku-X system. Get lots more applications to Haiku which would attract users + developers much sooner. X would be a 3rd party package like Qt (an add on).

I’m still undecided if X would be good or bad thing for Haiku. Hard to say. Qt may give enough programs that we may not need X on Haiku.

Also, remember that everyone is free to do what they want (with the code) even if you disagree with them or their direction.

12

[quote=tonestone57][quote=thatguy]I think your making a mess with X. X is a giant mess. I have no idea why anyone would focus on linux compatability. I would focus on windows interoperability.

In fact a great fork could be a deep wine intergration. bringing X brings all the x problems. I wouldn’t do it, microsoft and many other systems get by just fine without that albatross.[/quote]

Because SDL X can be done fast and easy. That’ll give access to lots of Linux software because the GUIs are done in X and will require minor changes to work with Haiku’s kernel.

Also, with X, he could do WINE using X which would get WINE onto Haiku faster. A native port of WINE will take very long time to happen. So, if someone said they could get you WINE in 6 months but using X would you say yes or would people prefer to wait 3+ years for native version?

I stated in another post that bringing X to Haiku would get software like OpenOffice, WINE, FireFox, VirtualBox, …, onto Haiku the fastest. Of course it’ll get messy and not ideal but it would bring lots more software to Haiku the quickest. It would create a hybrid Haiku-X system. Get lots more applications to Haiku which would attract users + developers much sooner. X would be a 3rd party package like Qt (an add on).

I’m still undecided if X would be good or bad thing for Haiku. Hard to say. Qt may give enough programs that we may not need X on Haiku.

Also, remember that everyone is free to do what they want (with the code) even if you disagree with them or their direction.[/quote]

At the end of the day, adding X really destroys haiku. now you are back into linux land where not everything works well or play together nicely “not that haiku doesn’t have bugs” but that the current system and the way its built is solid.

My take on wine is that is should either become native or just not be brought over.

QT adds a huge amount of useful programs and the QT port is really well done. I don't see a future with X being anywhere near as productive or useful.
13

[quote=agreimann]Thank you for your input. I’ll consider it.

However, without X, a lot of Linux apps won’t run, and I want to aim for Windows and Linux compatibility. I do know that X has a lot of problems. And, also, I’m thinking of it being “launchable” like X11 on OS X–not to replace the GUI shell with X. :)[/quote]

      I don't regard most linux apps worth running, neither do most people. Generally speaking anatyhing available for linux is also available for windows. So if you get wine working. You solve both problems while leaving X where it belongs.
14

I noticed that this post, while intended to simply ask “How can I delete my account?” is morphing into different opinions and arguments about X… and I apologize for any trouble mentioning X11 may have caused.

However, while there is a strong point that we do not want the OS to be too much like Linux, and that many users will not care about Linux apps (only 0.8% use it), it is also important to remember that applications that require the X Window System would be built twice as fast with a launchable X11. For instance, at first, OS X didn’t have that many native OSS programs. The alternative used was to run programs with X11.

Should this be included? I don’t know… but I thought it might have been a good idea. And as for qemu or wine, that won’t happen until the build is stabilized.

@tonestone57: Notice I mentioned the kernel, and the bootloader, (but I also listed all the other mods like the icons as well)–but this is a fork.

15

After analyzing the actual possibilities of the system, I find that I need to re-evaluate a few things mentioned earlier, so that I know what can’t and what will happen.

Here is what will not be included:

After reconsidering it, X will not be included–(not only because of feedback on that)–but because it will involve a tangle of code and no interoperability. BeOS, Haiku, and Mac OS aimed to keep things simple–X would not keep it that way.

The “uncomplicated firewall” (ufw) will also not be included–it requires, and I quote pieces from Requirements in the README file, “/proc filesystem support…Linux kernel configured with the following modules…” Obviously, neither Haiku or the fork will meet these requirements.

What will happen with the fork:

  • Revamp icon scheme into a unique set
  • Compile wine with Haiku patch (thinking of an emulator as well)
  • Include Minefield and latest build of Arora

Hopefully, this post should be more accurate, and be a lot more realistic than the previous one I posted.

16

I agree on this. It will probably make it a hassle. If you want simple Linux compatibility, maybe you can consider Wayland support in the future.

You should be careful with a Wine port. Wine is pretty much an emulator (though it emulates API’s and not hardware), so you need to think about latency for example if you want it to work well. The easiest route is probably to use the SDL sound driver, but I suggest you work on native media_kit integration as soon as you get it running, to avoid having too many layers. If you do it well I can’t wait to try it. Wine is a great project IMO.

17

[quote=agreimann]After analyzing the actual possibilities of the system, I find that I need to re-evaluate a few things mentioned earlier, so that I know what can’t and what will happen.

Here is what will not be included:

After reconsidering it, X will not be included–(not only because of feedback on that)–but because it will involve a tangle of code and no interoperability. BeOS, Haiku, and Mac OS aimed to keep things simple–X would not keep it that way.

The “uncomplicated firewall” (ufw) will also not be included–it requires, and I quote pieces from Requirements in the README file, “/proc filesystem support…Linux kernel configured with the following modules…” Obviously, neither Haiku or the fork will meet these requirements.

What will happen with the fork:

  • Revamp icon scheme into a unique set
  • Compile wine with Haiku patch (thinking of an emulator as well)
  • Include Minefield and latest build of Arora

Hopefully, this post should be more accurate, and be a lot more realistic than the previous one I posted.[/quote]

I wish you much luck in your efforts. There has been some conversation about a wine port over at www.haikuware.com

Might be a bounty involved if you made your wine build is capable of being put into the regular version of haiku.

18

[quote=agreimann]I noticed that this post, while intended to simply ask “How can I delete my account?” is morphing into different opinions and arguments about X… and I apologize for any trouble mentioning X11 may have caused.

However, while there is a strong point that we do not want the OS to be too much like Linux, and that many users will not care about Linux apps (only 0.8% use it), it is also important to remember that applications that require the X Window System would be built twice as fast with a launchable X11. For instance, at first, OS X didn’t have that many native OSS programs. The alternative used was to run programs with X11.

Should this be included? I don’t know… but I thought it might have been a good idea. And as for qemu or wine, that won’t happen until the build is stabilized.

@tonestone57: Notice I mentioned the kernel, and the bootloader, (but I also listed all the other mods like the icons as well)–but this is a fork.[/quote]

the Koffice port already has a functional somewhat X implementation. runs like crap.

19

X is not going to be included… so you don’t need to worry about any “mess” if X is installed that you are describing.

20

I was just stating that X has been run on haiku, well the koffice port.

anyways there is some source code for the bewine “be version of wine” in the winde source tree or on source forge. Its also on Haikuware. I think the source might be there to.

I have no idea how good/bad etc it was and how it was built.

But it might prove to be a starting point to get things working.

Just trying to help ya along in your quest.

You could also hit the mailing list. A few of the devs I think have worked on a wine port on and off for a while.

Like I said there is talk of a wine bounty, not that its been started but alot of us would love to have a good native wine that could be upstreamed to wine for building.

Go for it man.