|(25 intermediate revisions by 8 users not shown)|
The coreboot project currently runs two mailing lists:
* For questions and general information about coreboot, please subscribe to the [ http: //www. coreboot.org /mailman/listinfo/coreboot coreboot mailing list]. Note: The coreboot mailing list currently gets an average of about 1000-1500 mails per month.
the [:..org]. list
* If you want to get brief news about coreboot's progress, please subscribe to the [http://www.coreboot.org/mailman/listinfo/coreboot-announce coreboot-announce mailing list]. This list is moderated and will only get very few mailing list posts per month.
to , . This .
You can also contact us via [ [IRC] ] if you prefer that.
== Archives ==
== Archives ==
A mailing list archive dating back as far as August 2002 can be found at http://www. coreboot.org/pipermail/ coreboot/.
A searchable (but incomplete) archive is available at http://www.mail-archive.com/ linuxbios@ clustermatic.org/.
* Yet another ( searchable) archive is available at http:// blog. gmane.org/ gmane. linux. bios/.
Flashrom related mails are welcome on the flashrom mailing list at firstname.lastname@example.org. Please do NOT send any BIOS images or F segment dumps to the list!
E-mails with binary files attached will be rejected. Images for things such as scope or logic analyzer traces are acceptable if hosted on a third-party photo sharing service that assigns a unique URL to the image, such as Google Photos. This prevents the photo URL from being abused for malicious or inappropriate content.
Please note that the list is moderated for non-subscribers and we recommend to subscribe first.
If your mail is too big (the current limit is 256 kB) or if you're not on the subscriber list, your mail will be held for moderation. If your mail contains any BIOS images or F segment dumps (instead of links which are fine), the mail will be rejected for legal reasons (we do not have the right to distribute BIOS images).
Moderation howto for moderators.
Some of the flashrom developers and users hang out in the #flashrom channel on the Libera.chat IRC network. If you don't have an IRC client, you can use the Libera.chat webchat.
Here you have the chance to talk to people being involved or interested in this project. Most of the discussion is tech talk and user help.
Do note that IRC's nature has a significant effect on conversations. People from all over the world can join this channel, with many different cultures and timezones. Most people are in the CET timezone, so the channel may be very quiet during CET nighttime.
If you have a problem and would like to get help, don't ask for help. Instead, just explain your problem right away, and make sure to describe the situation as much as possible, so that other people can understand you and provide meaningful answers. Otherwise, others have to ask or guess the details of your problem, which is frustrating for both parties.
If you receive no replies, please be patient. After all, silence is better than getting replied with "IDK". Frequently, somebody knows the answer, but hasn't checked IRC yet. In any case, please do not leave the channel while waiting for an answer! Since IRC does not store messages, replying to somebody who left the channel is impossible.
To have persistence on IRC, you can set up an IRC bouncer like ZNC, or use IRCCloud. Please do not publish any logs of this channel.
Most of the time, people use IRC on wider-than-tall screens. Because of this, consider that pressing the return key is expensive. Instead of sending lots of tiny messages with only about two words, prefer using longer sentences, spaces and punctuation symbols. If reading and understanding your messages is easy, replying to them is also easy.
Should you need to paste lots of text (more than three lines), please use a paste service. For flashrom logs, feel free to use paste.flashrom.org. Other good paste services are ix.io, paste.rs, bpaste.net, gist.github.com and dpaste.com.
Questions on coreboot, OpenBIOS, firmware and related topics are welcome in #coreboot on the same server.