Commit c1002101 authored by Nick Wellnhofer's avatar Nick Wellnhofer
Browse files

Update information about contributing

The contents of the HACKING file were hopelessly outdated. Remove the
file and start with a CONTRIBUTING document.
parent b2189571
The current version of the code can be found in the GNOME Git Repository:
https://git.gnome.org/browse/libxml2/
There's mirror on GitHub:
https://github.com/GNOME/libxml2
Start discussions and send patches to the mailing list, or file a bug and
add a patch as attachment.
https://mail.gnome.org/mailman/listinfo/xml
https://bugzilla.gnome.org/enter_bug.cgi?product=libxml2
Format patches with git-format-patch and use plain text attachments
if possible.
All code must conform to C89 and pass the "make check" tests. Avoid
compiler warnings and add regression tests if possible.
The .travis.yml file can be used to thoroughly check the build with strict
compiler flags, ASan and UBSan. Fork the libxml2 mirror on GitHub and set
up Travis to test the commits you make on your fork.
NOTE:
- the head of this module is package libxml-2 . There is incompatibilities
with the old libxml-1 headers. I posted on gnome-hackers a recipe to
change your code to compile with both, check it out ! Also read
http://xmlsoft.org/upgrade.html
- in the meantime the old 1.x code has been tagged with LIB_XML_1_BRANCH
extract this version and drop me a mail if you want me to take care of
the update of your module to libxml-2 <daniel@veillard.com>
- the 1.x branch has a separate commit policy, please check the HACKING
file for this branch
Rules for commits on the gnome-xml module
=========================================
BEFORE READING FURTHER: DO NOT COMMIT DIRECTLY !
In the exceptional case where a serious breakage in this module
prevents other core projects from making progress, then feel free
to patch first and send mail afterward as long as the changes are limited.
Please keep in mind that a large part of my user base is on Windows, so
be careful with potential portability problems there.
Otherwise, send me (veillard@redhat.com) a mail and if it's a bug
issue, register it at bugzilla.gnome.org (module libxml). I check both
my mail and the bug database on a regular basis. If you don't get an
answer within a week (which is highly unprobable) then commit your changes.
This simply mean that I'm on holliday or on the road.
thanks in advance for following the rule,
Daniel
P.S.: Bjorn Reese, William Brack, Thomas Broyer, Igor Zlatkovic and
Aleksey Sanin get an exception for the send before commit rule
as well as John Fleck for the doc maintenance Send them mail if
I don't answer to request in a timely fashion
Please read the HACKING file for instructions
Please read the CONTRIBUTING file for instructions
Daniel
......
......@@ -34,7 +34,7 @@ fi
# Copy some documentation files if needed.
for TEXT in "${TOPDIR}/AUTHORS" "${TOPDIR}/ChangeLog" \
"${TOPDIR}/Copyright" "${TOPDIR}/HACKING" "${TOPDIR}/README" \
"${TOPDIR}/Copyright" "${TOPDIR}/CONTRIBUTING" "${TOPDIR}/README" \
"${TOPDIR}/MAINTAINERS" "${TOPDIR}/NEWS" "${TOPDIR}/TODO" \
"${TOPDIR}/TODO_SCHEMAS" "${TOPDIR}/os400/README400"
do if [ -f "${TEXT}" ]
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment